Individuals&#39; URL identity exchange and communications

ABSTRACT

A system for individuals&#39; representation and data exchange using URLs with the individual&#39;s name as the subdomain and his affiliated organization as the domain. The URL has individual&#39;s information privacy control, exchangeable data, and spam-resistant communications channel. Exchange websites can use such individuals&#39; representations, examples being contacts management system, eCommerce exchange systems, matchmaking services and discussion forums. Branding assessments result from using the system.

CROSS-REFERENCE TO RELATED APPLICATIONS

[0001] This application claims the benefit of U.S. ProvisionalApplication serial No. 60/400,270 filed on Jul. 31, 2002 by Chen Sun andU.S. Provisional Application 60/475,716 filed on Jun. 4, 2003 by ChenSun.

[0002] This application is also a continuation in part of U.S.application Ser. Nos. 10/074,081, 10/189,063, 09/642,127, 09/853,167,and 10/190,283 and U.S. Pat. No. 6,442,602

TECHNICAL FIELD OF INVENTION

[0003] This invention relates to personal digital representation andidentity, web exchanges (marketplaces) that work with these, andcontacts management. The invention uses subdomains, URLs, andspam-resistant communications to represent an individual.

FEDERALY SPONSORED RESEARCH

[0004] Not applicable

SEQUENCE LISTING OR PROGRAM

[0005] Not applicable

INCORPORATION BY REFERENCE

[0006] U.S. applications Ser. No. 09/642,127 filed by Azkar Choudhry onAug. 18, 2000 and 10/190,283 filed Jul. 5, 2002; U.S. application Ser.No. 09/853,167 filed jointly by Chen Sun and Azkar Choudhry on May 11,2001; and U.S. application Ser. Nos. 10/074,081 and 10/189,063 filed byChen Sun on Feb. 1, 2002 and Jul. 2, 2002 respectively; are incorporatedherein by reference in their entirety, including drawings and anymicrofiche appendices, and are hereby made a part of this application.

BACKGROUND I. Individual Representation Using Web Handles

[0007] Many types of individuals' information exchange currently takeplace on the Internet, and frequently the individuals are represented byweb handles. For example, dating websites and discussion forumsfrequently represent individuals by web handles. Web auctions use webhandles to represent individual sellers and buyers. Examples are“fromglobaltoyou”, “browneyedgirl022”, “faithingintheprize”, “beauty25”,“lively505”, and “beach296” where these represent individuals.

[0008] A characteristic of web handles is that laymen web users caneasily register for one through filling out the forms sent by thewebsite involved. Another characteristic is that the web handle'sbranding, as well as its privacy (the degree of information that isreleased by the web handle) is within the website.

[0009] The disadvantages of handles are that these areunprofessional-sounding names and registering for these names takestime. Perhaps more importantly, once attained, a web handle's brandingvalue remains within the issuing website and doesn't carry to othersites or outside of the Internet.

II. Individual Representation Using Email Address

[0010] Another frequent form of individual representation on theInternet is email address. This form suffers from a number ofdisadvantages:

[0011] 1. email address gives a channel of communications, but conveysvery little individual information. That is, email address doesn't statename, title, occupation, etc.

[0012] 2. the current form of SMTP email is highly subject to emailspam, and studies now show that an average individual spends more timeclearing away spam than receiving legitimate email. Spam are largequantities of unsolicited emails, frequently sent by unscrupulouspromoters of pornography, get rich schemes, etc.

[0013] At present, the most common form of individual representation isthe paper business card, which frequently has SMTP email addressesprinted and are subject to being spammed. Once spam starts, SMTP emailbecomes difficult to manage and use.

III. Individual Representation Using URLs, Part 1

[0014] Using a URL to represent individuals would solve the brandingproblems of web handles, but would cause privacy and URL-naming controldifficulties.

[0015] Using a URL is illustrated in U.S. Pat. No. 6,085,242, “Methodfor managing a repository of user information using a personalizeduniform locator”, by Rohit Chandra, which uses an unique code placed infront of a domain for a individual representation in Chandra's system.As such, identically named subdomains cannot be used. For example,Chandra's invention cannot use several “Joe” as subdomains, as inJoe.GM.com, Joe.Ford.com, and Joe.Microsoft.com.

[0016] In a document TDB0901.0055 posted by IBM on “e-business cardsystem”, a URL is again used, with the example “e-buscard.ibm.com/12345.Here, the person's name is not in the URL, and there is no privacycontrol.

IV. Representation by URLs, Part 2

[0017] In patent applications Ser. No. 09/853,167by Chen Sun and AzkarChoudhry; Ser. No. 09/642,127 by Azkar Choudhry; and Ser. No. 10/189,063and Ser. No. 10/074,081 by Chen Sun, it is shown that virtual subdomainsaddresses, a type of URL, have a syntax of Subdomain.Domain, and canrepresent individual's information.

[0018] The problem remained that using Subdomain.Domain for individualidentification offered the individual limited privacy, as theindividual's information URL is easily accessible by anyone.

[0019] Privacy can be solved by using password protection on thesubdomain-domain displayed webpages. However, this would requireadditional steps in sending, memorizing, recalling, and typingpasswords.

[0020] Privacy can also be solved by adding a file suffix that is notknown to others. For example, addressing http:H/Joe.GM.com/56kje26 mayshow Joe's private deals that he offers only to customers, who know the“56kje26” private file suffix.

[0021] This Subdomain.Domain/FileDirectory syntax to represent anindividual can have many advantages including:

[0022] 1. Easy to verbally communicate personal contact information.

[0023] 2. eMail capable by adding http:// to SDFD and sending it as alink.

[0024] 3. Digitally manageable, as a SDFD can represent an addressableURL.

[0025] 4. Print version capable by printing from http://SDFD.

[0026] 5. Downloadable data to PCs through http://SDFD.

[0027] 6. eCommerce capabilities

[0028] 7. Exchangeable data

[0029] 8. Database information included

[0030] 9. Abundant information capable

[0031] There arises a need for an effective means of using URLs forindividual representation that is spam-resistant, is useful inexchanging information, and has privacy capabilities; and a need for webexchanges that can use such an individual representation.

OBJECTS AND ADVANTAGES

[0032] Several objects and advantages of the present invention are:

[0033] 1. a system of using URLvs (URL name without the protocol) torepresent individuals, easily communicated by speech, writing, anddigital technologies,

[0034] 2. such URLv representation also provides a degree of privacy forthe individual through file directory name change,

[0035] 3. a system of using such URLvs together with new exchangeablewebsites such that the individual can use his URLv to quickly registerin a website, saving him time and giving the website's an efficient wayof extracting information about the individual,

[0036] 4. a spam-resistant channel of communications to contact theindividual through or made known through URLv addressing,

[0037] 5. a system of branding the individual and his associatedorganization throughout the above, and

[0038] 6. a contacts management system using the above.

[0039] Further objects and advantages of my inventions will becomeapparent from a consideration of the drawings and ensuing description.

SUMMARY

[0040]FIG. 4 shows an overview of this invention's individualrepresentation-IWeb interaction. It comprises of the following, whichwill be explained later:

[0041] A system of nURLvs with the syntax of name-Subdomain-Domain (nSD)(1) and name-Subdomain-Domain-File Directory (nSDFD) (2), which can formwebpage profiles of the individual whose name is the subdomain's name,

[0042] A http://nSD webpage (3) containing a spam-resistant, publiccommunications channel, which can be as simple as a webpage form email,as shown (7),

[0043] The various ndfSDFD (df—data field) and nSD profiles can enter(4) into different IWeb (5) web individuals' exchanges sites, and thus,the individual's nSD carries branding and interaction across multipleexchanges and sites,

[0044] The various ndfSDpFD can have a privacy control system module(pcsm) (6) which enables named layman user to modify his FD whileretaining its original web content.

[0045] IWeb (5) websites with software services that allow forextraction and exchange of data fields of individual information usingndfSDFDAs, and

[0046] The branding (8) of the individual and his organization based onthe text of nSD.

[0047] Not shown is ndfSDpFDA's authorization process for IWebparticipation.

[0048]FIG. 12 presents a second overview.

BRIEF DESCRIPTION OF THE DRAWINGS

[0049] The figures presented herein when taken in conjunction with thedisclosure form a complete description of the invention, whereinelements and steps indicated by like reference indicators are the sameor equivalent elements or steps.

[0050]FIG. 1. Prior Art

[0051]FIG. 2. Prior Art

[0052]FIG. 3. Prior Art

[0053]FIG. 4. Overview of Invention

[0054]FIG. 5. Prior Art of virtual subdomain address file suffix (VSAFS)

[0055]FIG. 6. Prior Art display of VSAFS

[0056]FIG. 7. Privacy control system module embodiment-A

[0057]FIG. 8. Privacy control system module embodiment-B

[0058]FIG. 9. Privacy control system module embodiment-C

[0059]FIG. 10. Privacy control system module embodiment-D

[0060]FIG. 11. Privacy control system module embodiment-E

[0061]FIG. 12. Second overview of the invention

[0062]FIG. 13. How type 1 IWebContacts works.

[0063]FIG. 14. An embodiment of type 1-ndfSDpFDAs online

[0064]FIG. 15. An Embodiment of Type 1-nSDFDAs local

[0065]FIG. 16. A VSAFSserver (Prior Art)

[0066]FIG. 17. How type 2 IWebContacts works.

[0067]FIG. 18. A type 2 embodiment with local ndfSDpFDAs.

[0068]FIG. 19. A type 2 embodiment with ndfSDpFDAs online

[0069]FIG. 20. IWeb authorization process.

GLOSSARY

[0070] The URLv acronyms are formed by using abbreviations incombinations. This glossary provides a brief summary of theseabbreviations.

[0071] URLv (URL verbal) is a URL name without the protocol, hence theportion after the “http://”.

[0072] Abbreviations used in URLv—e.g. ndfSDpFDA

[0073] n is individual's name or representation of his name,

[0074] df indicates that its web content has exchangeable data fields

[0075] S is the subdomain

[0076] D is the domain

[0077] p indicates that the file directory has an associated privacycontrol system module

[0078] FD is a file directory

[0079] A (all) indicates that this URLv can be either a ndfSD or ndfSDFDwith the same individual's named subdomain and domain.

[0080] Other abbreviations used in URLv

[0081] FS is file suffix

[0082] FD/ is file directory with an ending “/”

[0083] FD and pFD—when used independently, implies nSDFD or nSDpFD.

[0084] A family of nSDFDAs includes all the same-nSD-prefixed nSD andnSDFDs. VSAFS—virtual subdomain address file suffix—a type of SDFS usingthe technology described in patent application Ser. No. 10/189,063.

[0085] privacy control system module (pcsm) allows laymen, including thenamed individual of a nSDpFD, to change nSDpFD's file directory nameeasily, while retaining the original web content.

[0086] hWeb is a prior-art type of website where individuals exchangeand share information with other individuals and this information maylead to other kinds of exchanging. Individuals have representation inthese sites, usually as web handles.

[0087] IWeb are software and sites similar to hWeb, with the primarydifference that its individual representation is a ndfSDpFDA or othernURLv forms.

[0088] nSD-text-as-identity—using the text portion of a nSD as anidentity in an IWeb.

DETAILED SPECIFICATIONS

[0089] We will explain the invention in these following sections:

[0090] I. Prior art of web server and the Internet environment

[0091] II. Overview of the invention as a system

[0092] III. (a-j) Naming-value of the preferred nURLv-ndfSDpFDA naming &design.

[0093] IV. (a-e) Information exchange methods between ndfSDpFDA andIWebs

[0094] V. (a- h) Privacy control system module on pFD.

[0095] VI. Spam-resistant public communications channel.

[0096] VII. Searchable index of nSDs with spam control publiccommunications channel

[0097] VIII. Second Overview

[0098] IX. Embodiment—IWebContacts, a contacts manager

[0099] X. Additional embodiments

[0100] XI. Impact of using ndfSDpFDA and Iwebs and more embodiments

[0101] XII. IWeb's Individual Identity

[0102] XIII. Branding characteristics of IWebs, ndfSDpFDA

[0103] XIV. ndfSDpFDA web content authorizes interaction with IWeb

[0104] XV. Variants

[0105] XVI. Summary

[0106] The attached glossary helps with the terminology.

I. Preferred Web Server and Overview of the Internet

[0107] The invention is preferably realized using an Apache HTTP (HyperText Transfer Protocol) Web Server as the basic platform. The Apacheserver is well known within the art, and is possibly the most popularweb server used today. Many webmasters are capable of configuration andinstallation of such a server, and they can be readily obtained fromcompanies such as Apache Digital Corporation of Durango, Colo.

[0108] FIGS. 1-3 are well known prior art; these figures are directlyfrom patent application Ser. No. 09/853,167 submitted May 11, 2001 byChen Sun and Azkar Choudhry. FIG. 1 (Prior Art) shows the well-knownInternet architecture of domain and subdomain servers. FIG. 2 (PriorArt) shows the well-known architecture of an Apache HTTP server. Theserver is a combination of a computer platform with specializedsoftware. The computer platform generally consists of a centralprocessing unit (“CPU”) with memory (21), one or more hard disk drives(“HDD”) (22), and a network interface card (“NIC”) (23). This may be anIBM-compatible personal computer, as in the preferred embodiment, or Sunworkstation or other suitable standard computer platform. A BasicInput/Output System (“BIOS”) and set of low level driver firmwaremodules (24) typically interfaces the higher-level software to thehardware, including a NIC driver. A multi-tasking operating system(“OS”) (25), such as Microsoft Windows NT, Linux, Unix or IBM OS/2, isalso installed on the computer platform. Linux is the operating systemof the preferred embodiment.

[0109] The Apache HTTP server software (27) is available for freedownload from the Apache Software Foundation at http://www.apache.org.It is an application program which interfaces to the Internet (1)through the NIC (23) and a Transmission Control Protocol/InternetProtocol (“TCP/IP”) communications protocol stack. The TCP/IP stack maybe native to the OS, or it may be supplied as a separate but compatiblemodule with the Apache application and the OS. Other applicationprograms (26) such as database engines, CGI scripts, Java servlets andPHP scripts may be executed on the same platform simultaneously to theApache HTTP server application. PHP/FI is a scripting language thatsupports dynamic HTML pages. It is similar to Apache's SSI, but morecomplex and has database modules for the most popular databases. PHP/FIis a product of Iquest Internet of Indianapolis, Ind. In the preferredembodiment, the NIC is a 100BaseT local area network interface card,interconnected to the Internet (1) via one or more routers.

[0110]FIG. 3 shows the well-known arrangement of Internet browsercomputers, Domain Name Servers (“DNS”), Internet Service Providers(“ISP”), and domain servers. The internal architecture of domain nameservers is fully described in RFC 1035. In general, when a user selectsa network address, such as “http://www.anycompany.com”, in his webbrowser software, the browser machine (30) transmits a request (A) tothe ISP (34). The ISP (34) then contacts (B) the DNS (32), which returnsa translation (C) of the text-based URL to a numerical IP address value.The user's browser then requests (E) a document from the domain server(33) located at the IP address given by the DNS. The domain server (33)transmits (F) the document, typically in HTML, to the browser machine(30) via the ISP.

II. Overview of the Invention in a System

[0111]FIG. 4 shows an overview of such individual representation-IWebinteraction. It comprises of the following, which will be explainedlater:

[0112] A system of nURLvs with the syntax of name-Subdomain-Domain (nSD)(1) and name-Subdomain-Domain-File Directory (nSDFD) (2), which can formwebpage profiles of the individual whose name is the subdomain's name,

[0113] A http://ndfSD webpage (3) containing a spam-resistant, publiccommunications channel, which can be as simple as a webpage form email,as shown (7),

[0114] The various ndfSDFD profiles can enter (4) into different IWeb(5) web individuals' exchanges sites, and thus, the individual's nSDcarries branding and interaction across multiple exchanges and sites,

[0115] The IWebs can manipulate the profiles information,

[0116] The various ndfSDpFD can have a privacy control system module(pcsm) (6) which enables named layman user to modify his pFD whileretaining its original web content.

[0117] IWeb (5) websites with software services that allow forextraction of data fields of individual information using ndfSDFDAs, and

[0118] The branding (8) of the individual and his organization based onthe text of nSD.

[0119] Not shown is ndfSDpFDA's authorization process for IWebparticipation.

III. Preferred nURLv Name Embodiment—ndfSDpFDA IIIa. Naming—Backgroundon URL Syntax

[0120] URLs (Uniform Resource Locators) are normally used for Internet'saddressing. A sample one ishttp://www.CompanyA.com/deptA/productA/specs.html . The “/”, ”.”, and“:” separate the characters, and the location of the characters have aname. “http” is the protocol. “com” is the top level domain name.“CompanyA.com”, the second level domain and also called the domain.Unfortunately, “CompanyA” without the ”.com” is also frequently calleddomain, and to clarify this, we will call “CompanyA”, adomain. The “www”is the subdomain (also known as third-level domain name).“deptA/˜productA/specs.html” is the file suffix and contains parts“specs.html”—the file name, and “deptA/˜productA/”—the file directory.Additional letters and separators “.” can be placed in front of thesubdomain to form sub-subdomains (fourth level domains),sub-sub-subdomains (fifth level domains), and so forth.

[0121] Unfortunately, both “/deptA/˜productA” and “/deptA/˜productA/”(with an ending “/”), are called file directories. File directorieswithout file names following can be used in a URL because web serversusually will supply a default file name, such as index.html. In thisapplication, when FD or FD/ (with an ending “/”) is used, it indicates afile directory using a default web content file. The exact details onhow to achieve this by its web server are known within the arts.

IIIb. Naming-Abbreviations Used in URLv Individual Representation

[0122] When URLs are spoken or printed, frequently the http:// isdropped, because http protocol addressing is predominant. For example,if the correct URL is http://Joe.GM.com/cars; then, when spoken,“Joe.GM.com/cars” is commonly verbally used. An URLv is a URL namewithout the protocol, hence the portion after the “http://”. URLv is theabbreviation for URL verbal, emphasizing that the verbal (spoken,written, printed) communications aspects of this invention are importantin its usage. A nURLv is a URLv with a person's name or representationof his name in the front of the URLv. The nURLv used in this inventionhas an individual's name or representation of a name in its third leveldomain name (subdomain), then also have second and first level domainnames, and may or may not have a file suffix.

[0123] Abbreviations are frequently used in this application to describeparts of and constraints of a URLv. An URLv subdomain-domain-file suffixcombination is abbreviated SDFS; subdomain-domain-file directorycombination is SDFD; subdomain-domain combination is SD. FSs includeFDs.

[0124] A more complicated abbreviation is ndfSDpFDA, where:

[0125] n is individual's name or representation of his name,

[0126] df indicates that its web content has exchangeable data fields

[0127] S is the subdomain

[0128] D is the domain

[0129] p indicates that the file directory has an associated “privacycontrol system module”

[0130] FD is a file directory

[0131] A (all) indicates that this URLv can be either a ndfSD or ndfSDFDwith the same individual's named subdomain and domain.

[0132] To best understand this invention from an URL technologyperspective, note that though many combinations of abbreviations arepossible, there are only three structural syntaxes in this inventionthat URL “technology” manipulates—SD (subdomain-domain), SDFD(subdomain-domain-file directory), and SDFS (subdomain-domain-filesuffix). Additionally, note that the http addressed entity of nURLv isusually a webpage, represented and located by a URL technology using SD,SDFD or SDFS. So, where a constrained form of SD, SDFD, or SDFS isstated below, it is generally implied, that from aURL-technology-manipulation perspective, broader forms of SD, SDFD, orSDFS can also be used. For example, if a ndfSDpFDA is used in a URL, aSDFD (the broader form) would also work in the URL. The exception iswhen df is included, and if an IWeb uses df (data fields), these will berequire dfs in the nURLv.

IIIc. Terminology Clarification

[0133] Identity is an individual's continual naming and will be seen asthe text of the nSD. An individual may have several identities by havingseveral nSDs. Profile is a web view of the individual—one of many nURLvs (ndfSDFDAs) that an individual may have. Sometimes “FD” or “FS” isindependently written as having a profile, and it is inferred that theseFD or FS have a nSD (e.g. nSDFD or nSDFS).

[0134] nURLv is a generic syntax, and the invention's preferredembodiment is ndfSDpFDA. nURLv embodiments can include ndfSDpFD, nSDpFD,nSDFD, nSD, nSDFS, ndfSDFS, ndfSDpFS, and higher level subdomains. IWebscan work with other nURLv syntax, as will be later explained, and thegeneral ideas of the IWeb and ndfSDpFDA interactions, which are part ofthis invention, can be read using nURLv and other nURLv forms instead ofndfSDpFDA. However, the spoken and written channels of communications ofthis invention are valuable. SD or SDFD represent the most efficient andsocially preferred means of spoken or written communicating of thisinvention's profiles. ndfSDpFDA adds data field exchange, naming, andprivacy enhancements to SD and SDFD, but do not interfere with theirspoken or written communications. Hence, ndfSDpFDA is the preferrednURLv form. The digital transmission and communications of the numerousother nURLv forms can be as efficient and usually the FD/ version ismore efficient than the ndfsDpFDA, but here, we are concerned with thespoken, written, and digital means of communications channels,particularly the former two, and thus, ndfSDpFDA is the best.

IIId. Terminology—hWeb and IWeb

[0135] A hWeb is a prior-art website where individuals exchangeinformation and this information may lead to other kinds of exchanging.hWebs have a representation entity for its individuals. Some examplesare: eBAY.com where web-handled-represented individuals exchangeinformation that leads to products and money exchanges; Matchmaker.comwhere web-handled-represented individuals exchange dating information;employment websites where email-address-represented individuals exchangeresumes for employment opportunities; and web discussion forums whereweb-handled-represented individuals exchange their views.

[0136] IWeb is a type of website or software that uses a nURLv(preferably ndfSDpFDA) as its method to identify and representindividuals. IWebs can be constructed by modifying prior art hWebs orcreated independently.

IIIe. Naming Step 1—nSD—Social Parallels of “Name.Organization” and“Subdomain.Domain”

[0137] In step 1 of forming the name of the preferred nURLv, we willshow the semantic naming association of an individual's name to hisorganization and its social parallel to the named-subdomain-and-domaincombination.

[0138] Individuals have social meaning as part of an organization,whether this is an employee within a company, a citizen within a city, amember within an association, and many other forms ofindividual-organization. In this application, “organization” is definedas any groups of people, including businesses, non-profits, charities,informal associations, cities, states, nations, clubs and evendescriptions of classes of people. These organizations frequently havewebsites with their organization's domain name.

[0139] One way of creating a naming system for individualrepresentations is by associating an individual's name (Name) with hisorganization name, using the syntax “Name.Organization” or“Organization/Name.” For examples, “Florence.RedCross” or “NASA/John”.When “Organization” is replaced by the Organization's domain name, thisrepresentation can be “Name.Domain” or “Domain/Name.” For examples,Florence.RedCross.org and NASA.gov/John. Individuals will generallyprefer Name.Domain over Domain/Name because their name is first.Name.Domain is also more useful in marketing because the individual willtend to promote his representation better having his own name first.

[0140] Name.Domain abbreviated in URLv is nSD. A little letter “n” addsa constraint to SD, SDFD, or SDFS that the subdomain is an individual's“name” or “representation of an individual's name”. An example of nSD isJoe.GM.com, where “Joe” is the individual's named subdomain, “GM.com” ishis associated domain. An example of nSDFD can be Joe.GM.com/sedans,where “sedans” is his file directory of sedans.

IIIf. Naming Step 2-nSD, nSDFD, and nSDFDA Family—IndividualRepresentation & Identity (nSD) and His Profile Representations (nSDFD)

[0141] In step 2 of forming the name of the preferred nURLv, we willexplain the need for the benefits of subdomain for continual identityand multiple file directories as privacy control in representation.

[0142] The nURLv syntax structure portion “nSD” (named subdomain.domain)can be used as an individual's representation and identificationbecause, when compared to the latter portion (“FD” & “FS”—which relateto URL file suffixes), the “nSD” is relatively unchanging, thusproviding continual identification. It is relatively unchanging because,from a technology perspective, after the named subdomain is registeredas a subdomain, changing it usually requires some degree of technicaleffort by the domain administrator. Additionally, there are technicalissues on DNS update propagation delays, which makes changing subdomainsunfavorable. On the other hand, the file suffix portion is frequentlyand quickly changed by programmers and administrators.

[0143] Though an individual representation and identity system can usethe nURLv syntax nSD, such a system lacks a degree of privacy for thenamed individual, because all the web content of http://nSD would beviewable by all those who know such URL. An URL's file directory name(FD) can provide privacy when the file directory is privately known. Forexample, Joe of GM.com may have an unusual file directory name, eg“56kje26”. http://Joe.GM.com/56kje26, is privately known only to hisspecial customers, and when addressed would show a web page of Joe's GMspecial car offerings. As long as his special customers keep this URLprivate, the URL remains private.

[0144] FDs can also show different profiles of information about anindividual, and a FD without any additional “/”is, of course, theshortest and easiest way to communicate file suffix and file directory.For example, Joe of GM.com can have Joe.GM.com/Buick, Joe.GM.com/Chevy,Joe.GM.com/sedans, and Joe.GM.com/56kje26, each showing a differentprofile of Joe's car offerings. These FDs “Buick”, “Chevy”, “sedans”,and “56kje26” are brief and easy to communicate.

[0145] A SDFDA (A meaning All) is a SD or its same-SD-prefixed SDFDs.And a family of nSDFDAs includes all the same-nSD-prefixed nSD andnSDFDs. So, here Joe of GM.com's nSDFDA's family includes Joe.GM.com,Joe.GM.com/Buick, Joe.GM.com/Chevy, Joe.GM.com/sedans, andJoe.GM.com/56kje26.

[0146] The techniques for creating http://nSDFD are known within thearts. In one technique, a web server administrator places anindividual's name as a subdomain name in the domain's DNS tables, setsthis subdomain to a web server address. At the web server, he can createa directory in the domain by using “mkdir” command or create a directoryusing a FTP software, such as wsftpro, which can be downloaded fromwww.ipswitch.com. A file capable of supplying web content to browsers isplaced in this directory. This file is given the name of the webserver's directory default file name. Patent application Ser. No.10,189,063, “Virtual Subdomain Address File Suffix”, by Chen Sun showsanother version—using virtual subdomain address file suffix, where thesubdomain name is not within the DNS tables. Despite these threedifferent addressing or creation mechanisms, a nSDFDA's syntax remainsthe same.

IIIg. Naming Step 3—nSDpFD—pFD Privacy Control System Module (pcsm)

[0147] In step 3 of preferred nURLv name development, we will see theneed for a privacy module. Once the FD of a private nSDFD is known tothose outside the intended private parties, the http://nSDFD has lostits privacy value. To enable for profiles privacy, the individual needsto change his file directory name while retaining its original webcontent. A lower case letter “p” adds the constraint to nSDpFD that theFD also has an associated easy-to-use FD name change process thatretains its original web content.

[0148] Laymen using the web haven't been able to change or move FDs muchbecause URL design is typically under the control of and requires thehigh-in-demand-time of web administrators and programmers. Theinvention's privacy control system module (pcsm) will allow for laymen,including the named individual of a nSDpFD, to change nSDpFD's filedirectory name easily, while retaining the original web content. Thus,individuals attain FD privacy control without using programmers andadministrators' time.

IIIh. Naming Step 4—ndfSDpFDA—Web Content has Data Field Information(df)

[0149] In step 4 of the preferred nURLv naming, data fields areincluded.

[0150] HTML forms the majority of web content, and HTML is usuallywithout structured database fields (data fields). In the preferred nURLvembodiments, the web content of an addressed nURLv has data fields.IWebs can extract information from such data fields. “df” in a ndfSDpFDAindicates that data fields are available in the web content.

IIIi. Preferred nURLv Name Embodiment—Advantages of ndfSDpFDA inIdentification, Representation and IWeb Exchanges

[0151] The ndfSDpFDA formed through the above four steps is thepreferred nURLv because it has a number of advantages useful forindividual representation as well as for exchange with IWeb. We saw thereasons why ndfSDpFDA is preferred through its construction above,summarized below:

[0152] 1. each ndfSD is unique (due to DNS) and relatively unchanging,which helps to continually identify the person across multiple IWebs aswell as throughout the Internet.

[0153] 2. the ndfSDpFDA family can have multiple profiles, each of whichcan provide privacy and convey different profiles of information.

[0154] 3. the pFD has an associated process that enables the privacy tobe maintained by allowing laymen to change the file directory name whileretaining the original content.

[0155] 4. the df allows for data field exchange with IWebs, forming newweb marketplaces and communities.

[0156] 5. The ndfSDpFDA can easily be communicated verbally(orally), inwriting, or through digital transmission.

[0157] In addition, as a ndfSDpFDA is a URLv, it also has furtheradvantages:

[0158] 6. eMail capable by adding http:// to ndfSDpFDA and sending it asa link.

[0159] 7. Digitally manageable, as a ndfSDpFDA can easily form anaddressable URL.

[0160] 8. Print version capable by printing from web content ofhttp://ndfSDpFDA.

[0161] 9. Downloadable data to computing devices throughhttp://ndfSDpFDA.

[0162] 10. eCommerce capabilities.

[0163] 11. Database information capable

[0164] 12. Abundant information capable.

IIIj. Naming—Syntax Constraints—“n”, “p”, “A”, “df”

[0165] The letters “n”, “A”, “p”, and “df” added to SDFDs do not changethe URLv structure, but only add constraints to the subdomain, filedirectory, or web content. Also, as should be obvious, namingcombinations with these constraint letters are subsets of the URLvswithout these constraints-hence ndfSDpFD is a subset of a nSDpFD, whichis a subset of SDpFD, which is a subset of SDFD. The two followingexamples show how, from a URL technology manipulation perspective, SDFDstructure can remain the same when used in URL addressing, despiteconstraint letters added.

[0166] A ndfSDpFDA is designed to interact with an IWeb. An IWeb doesnot have a “technology” way of knowing whether a ndfSDpFD has a person'sname or name representation as the subdomain because the “n” definedabove is a social convention. So, the IWeb can technically use anydfSDpFDA.

[0167] An IWeb generally does not reliably know the difference between aSDFD and a SDpFD. This is because once a URLv is Internet addressed, thehttp data communications and IWeb generally doesn't distinguish betweenwhether the file directory had been created by a privacy control systemmodule or not. So, the IWeb generally can use SDFD or SDpFD similarly.

[0168] So, where a constrained form of SD, SDFD, or SDFS is statedbelow, it is generally implied that from a URL-technology-manipulationperspective, broader forms of SD, SDFD, or SDFS can also be used. Theexception is when df is included, and if an IWeb uses df (data fields),these will be required.

IIIk. Economic, Social, Marketing, and Technical Differences BetweennDFD and nSDFD

[0169] nDomain/file-directory URLv (nDFD), where the second level domainrepresents the individual's name can technically accomplish most ofnSubdomain.Domain/File-Directory (nSDFD) capabilities. However,relatively few individuals have adopted using nDFD for a number ofreasons. First, domain name ownership and website hosting are costly andtime-consuming. For example, website hosting company typically charges$25 per month for domain registration and website hosting. The samedomain hosting service fee can typically provide for magnitudes moresubdomain names and their hosting; thus, if 1000 subdomains were used,each individual's allocated cost is 2.5 cents per month. Second, websitedevelopment, upgrade, and maintenance can be very costly for theindividual. When the individual's nSDFD is tied to an organization, theorganization pays for the subdomain website development, upgrade, andmaintenance and spreads out its cost among its many individuals. Third,the syntax of the Name.Domain/Profile (nSDFD) is valuable, because itgives a way of identifying the individual with his associatedorganization, which reflects more of the social workings ofcivilization. A nD/FD profile syntax reflects the individual, butdoesn't reflect his organizational affiliation. Socially, a person hasmeaning within organizations; hence, the Name.Organization/Profilesyntax parallel to Name.Domain/FD (nSDFD) syntax is valuable. With thelower costing, lower maintenance, organizational affiliation, privacycontrol, and personal naming, the individual will adopt and usendfSDpFDA syntax more.

[0170] We can use eBAY.com to illustrate this. If an eBay.com individualseller used his individually owned nD/FD as identity for eBay's webhandles, he would pay his website hosting company $25 per month. Addthen web content management time and costs. Using the ndfSDpFDAidentities, the same $25 per month can provide magnitude times moresubdomain names and subdomain web content hosting. The web contentdevelopment and operational costs are shared among the numeroussubdomain owners. The organization affiliated with the individualabsorbs these costs and spread it among its users; hence, the costs peruser can be magnitudes less. If the seller had many sales reps, eachwould carry his own ndfSDpFDA associated with his organizational domainname. The ndfSDpFDA syntax will be much more popular because it issignificantly less in price and time costs and more reflective of theindividual-organization relationship.

IV. Exchange Interaction between ndfSDpFDA and IWebs IVa. Data ExchangeCommunications Methods between http://ndfSDpFDA and IWeb

[0171] A ndfSDpFDA is designed to be used with an IWeb, and their datacommunications methods need to be explained. HTTP is a statelessprotocol. HTML is primarily a style language, dealing with theappearance of the information, and it doesn't have much exchangeabledata field structure. As a result, programming techniques for data fieldtransfers and for database manipulations can be complicated. We willdiscuss below the various means ndfSDpFDA data communicate with IWebs.

[0172] The methods of data communications between the IWebs and thendfSDpFDA are important because these affect speed, reliability, andaccessibility to data fields; hence, several options are presented. EachIWeb may want its own method of communicating with the ndfSDpFDA, soeach communications pattern and the data received may be different. AndfSDpFDAserver is a server that can generate ndfSDpFDAs.

IVb. Method #1 in Data Communications

[0173] One method of communicating between the ndfSDpFDA and IWebs is touse HTML comment tags “<!—comment—>”, with the comments set as “datafield descriptors”. We can use business card information, from Table 1below (Section IX), as an example. If an IWeb addresses ndfSDpFDABobJones.CompanyA.com/biz, CompanyA.com's ndfSDpFDAserver responds bysending Bob Jones's contacts data attached with comments that serve asfield descriptors—“contacts information data <!—its data fielddescriptor—>”, as below:

[0174] Bob <!—FirstName—>

[0175] Jones <!—LastName—>

[0176] CompanyA <!—CompanyName—>

[0177] Accountant <!—Occupation—>

[0178] bobjones@companya.com <!—email—>.

[0179] IWeb's nURLv search and extract facility can search andmanipulate on these types of contacts data. Comment fields areadvantageous because the IWeb and browser can both address the samehttp://ndfSDpFDA, and the former receives and manipulates on thecommentary data field descriptors and data, while the browser doesn'tdisplay the commentaries.

IVc. Method #2 in Data Communications

[0180] XML, unlike HTML above, is designed to facilitate data structuresand searchable data. A more elegant, but perhaps more difficult toimplement method, is that the addressed ndfSDFDA and IWeb searchfacility communicate through using extended markup language (XML),instead of the HTML commentaries above. XML can identify data types. Forexample, when a ndfSDpFDA request for BobJones.CompanyA.com/biz is made,the ndfSDpFDAserver can return XML like the following.

[0181] <PERSON>

[0182] <NAME>

[0183] <FIRST>Bob</FIRST>

[0184] <LAST>Jones</LAST>

[0185] </NAME>

[0186] <COMPANY>CompanyA</COMPANY>

[0187] <OCCUPATION>Accountant</OCCUPATION>

[0188] <EMAIL>bobjones@companyA.com</EMAIL>

[0189] </PERSON>

[0190] The IWeb search facility can now examine the “Occupation” fieldand determine whether it contains “Accountant”.

IVd. Method #3 in Data Communications

[0191] Another standard to transfer data between ndfSDpFDA and IWebsearch facility can be that the ndfSDpFDAservers will release onlystandardized data formats. For example, a standardized business cardformat with only First Name, Last Name, and Company information. TheIWeb search facility will only search on these standards. Hence, if thevarious ndfSDpFDAs' HTML responses have identical formats, the receivingIWeb search facility can parse out the various contacts data fields.

IVe. Method #4 in Data Communications

[0192] It is possible that the IWeb software and all the ndfSDpFDAs thatit uses originate on the same host. In these cases, the datacommunications between IWeb and ndfSDpFDAs would not require http.Various local database programming techniques can be used to transferdata between these.

V. Privacy Control pFD in Various nURLv, and Particularly in ndfSDpFDA

[0193] Sections Va-j below describe a pcsm system that enable layman tochange his file directory name while retaining the original web contentof a nURLv. Note in these the importance of an nURLv syntax form being asubset of another. For example, if a pcsm file suffix change will workfor a nSDFS (name-subdomain-domain-file-suffix), it will also work for andfSDFDA, because the df and FD represent subset elements.

Va. The “p”, Privacy Control System Module (pcsm)

[0194] The “p”, privacy control system module, will be detailed below.Web administrators and programmers know how to change file directorynames while retaining the original content, but, here, we are interestedin a layman being able to accomplish this. In the design of the pFD,there needs to be layman-user-friendly ways of changing the filedirectory name while maintaining the same web content, ways of ensuringthat the URL formed is a legitimate URL, and ways of changing thepreviously linked from the same ndfSDpFDA family.

[0195] Many problems can arise if laymen are allowed to create or revisefile directories to be used in URLs.

[0196] 1. Web server security and server administration problems mayarise when laymen are allowed to create, delete, or redirect filedirectories.

[0197] 2. The standard URL syntax requires certain characters thatlaymen are likely to err when creating file directories.

[0198] 3. A FD-redirection mechanism may be more lax on the in-use URLsyntax than standard URL syntax, but many browsers may not acceptcertain components of the more lax version, and laymen may not know howto test this.

[0199] 4. The file directory web content may be database created, andchanging the directory would be a very different and difficult processthan simply moving files and creating directories.

[0200] 5. The ndfSDpFDA is an entire individual representation, andchanging the file directory may also involve affecting the subdomain.

[0201] 6. The original FD may be linked from other webpages in thendfSDpFDA.

[0202] 7. If a web server redirection and aliasing mechanism isdeployed, such as by Apache's mod_alias or mod_redirect modules, theproblem still remains that laymen would have difficulties in using sucha module.

[0203] 8. The FD may already have a redirection.

[0204] 9. The layman may not know the default file name.

[0205] The preferred nURLv embodiment (ndfSDpFDA) contains a pcsm. Apcsm consists of a private access point (e.g. password access) where theuser can attain access to a FD change mechanism. This change mechanismconsists of the user choosing a second FD name and associating thesecond FD addressing to the original FD's web content. Then, pcsmrevises the original FD and its web content such that http addressingusing the original nSDFD results in either a URL not found (an erasureof the original FD) or a URL redirection not to the second nSDFD.

[0206] If the original FD web content is a default file in a standarddirectory, then the above paragraph explains the pcsm process for thistype of nSDFD content.

[0207] If the original FD web content is dynamically formed by adatabase, the pcsm still has the private access for the layman and thenan easy process for attaching the second FD name to the original FDname's web content or process. As an example, the layman has a specialpassword entry to a FD change process in the database. Here, he simplynames the second FD and associates it to the original FD's action scriptthat created the dynamic database web content. The database would takeactions to create the second FD content using the original FD webprocess or content. Then the database would affect the addressing of theoriginal FD's nSDFD such that it would result in either a URL not foundor a URL redirection not to the second nSDFD.

[0208] If the original FD web content is formed involving a redirection,the pcsm still has the private access for the layman and then has aneasy-to-use process for mapping the second FD name to the original FDname's redirected web content or process. As an example, the layman hasa private password entry to a FD change process in the redirectionmechanism. Here, he simply names the second FD and maps it to theoriginal FD's redirected action script that created the original webcontent. The original FD's redirection mapping would be revised suchthat it would result in either a URL not found or a URL redirection notto the second nSDFD.

[0209] The pcsm has a “URL-name checking process” which checks thelayman's inputted second FD name for the below possible URL errors and,if unacceptable, advises the layman to correct his second FD name. Forexample, the layman might make the following errors:

[0210] 1. Placing extra “.” In the file suffix.

[0211] 2. Placing a “\” (from MSDOS) rather than a “/”.

[0212] 3. Placing an ending “/” and not realizing that many people wouldnot use such a “/” when using the ndfSDpFDA.

[0213] 4. Including “unsafe” characters, as described in Request ForComment 1738, by Tim Bemer Lee and others “Uniform Resource Locators(URL)”. These can include “space”, unnecessary “.” or “/”, “#”,graphical characters, and other. http://www.w3.or/Addressing/rfc1738.txt

[0214] Additional possible laymen errors are:

[0215] 1. Not copying across the index.html or other default file.

[0216] 2. Not knowing the name of the web server's default file

[0217] The pcsm can optionally update the original FD-URL links in thendfSDpFDA's family pages to be the second FD-URL links. Pcsm updates bysearching and replacing the original FD-URL links in the ndfSDpFDAfamily with the second FD-URL.

[0218] Search engines can index URLs, and it might be said that andfSDpFDA has little privacy because search engines will reveal FDinformation. There are several factors that reduce the risk of beingfound by search engine robots. Many http://ndfSDpFDAs are not linked toother URLs on public, robot accessible (e.g. password protected)webpages, and a search engine robot find is difficult. In some cases, itis possible to place in the http://ndfSDpFDA webpage metataginstructions a request that the search engine robots not index the page,and most search engine robots will honor this request. Note still thatthe file directory change privacy control is inherently a low-levelprivacy device as it primarily relies on the formed URL not being foundby inappropriate parties.

Vb. The VSAFS as a Type of SDFS (Prior Art)

[0219] Patent application Ser. No. 10/189,063, “Virtual SubdomainAddress File Suffix” (VSAFS), filed Jul. 2, 2002 by Chen Sun shows adfSDFS (ndfSDFD is a subset of dtSDFS). FIG. 5 is Ser. No. 10/189,063'sFIG. 7 and explains how a VSAFS is formed. FIG. 6 is Ser. No.10/189,063's FIG. 8 and shows how VSAFS are displayed. Full explanationof these figures is included in Ser. No. 10/189,063.

[0220] As shown in FIG. 5, a VSAFSserver sends a form to user (12),which the user fills out to request a SDFS combination (13-15). In thisrequest, he chooses (16) an action script to associate with his filesuffix. (19) to (23) is the process whereby the individual's chosenaction script option determines which subsequent form is sent (20A or20B) and which database is populated (23A or 23B). The special server(VSAFSserver) (20A & 20B) sends the user a form (21A or B) to use topopulate database fields (23A or B), which will create the associatedweb content to the action script. Then the SDFS and its action scriptare mapped (24-26). Hence a SDFS combination is formed, and can bedisplayed, as FIG. 6 shows. Full details of how a VSAFS is created anddisplayed are explained in patent application Ser. No. 10/189,063.

[0221] A little more about the VSAFS, as it relates to ndfSDFDA. Byapplying a rule that the subdomain of a VSAFS is a name orrepresentation of a name, nVSAFS is a nSDFS. A VSAFS automatically hasdata fields, so a nVSAFS is also a ndfSDFS. Because a VSAFS usesredirections in its file suffix, it is easy to use only file directorynames for the file suffix (by redirecting the file directory name to anactual file name), thus forming a ndfSDFD. And in the below section, wewill see a privacy module added, creating a ndfSDpFD using these VSAFS.The ndfSDpFDA is also created, since a VSAFS, as shown in FIG. 5, has anull file suffix option (19), which creates a VSA, which can become andfSD. Pat. No. 6,442,602 and patent applications Ser. Nos. 09/642,127,09/853,167 by Chen Sun and Azkar Choudhry explain how VSA are created.

Vc. pFD Embodiment VSAFS With FS Change Process

[0222] A process for a SDpFS is shown in FIG. 7, where steps 15 a, 16 aand 18 a have been added to FIG. 5. Having already set up a VSAFS, theindividual can now reenter at step 15 a through using a password.Individual then proceeds through steps 15, 16 a, and 16, keeping theoriginal action script, but changing the file suffix name. A pcsm checkis made on correct FD-URL formation (including URL syntax) of this name(16 a). If the URL and other pcsm checks are accepted, the processcontinues to step 16, 17, and 18. If not, the user is asked to chooseanother file suffix name at step 15. In step 18 a, the system determineswhether a new action script has been requested, and if so, to inquirefor more database information by proceeding through 19 to 23. If no newaction script has been requested, and the file suffix is a revision,then the file suffix name will change by continuing to steps 24 and 25.Step 25 would map the new file suffix name to the original file suffix'saction script of the VSAFS.

[0223] For example, http://Joe.GM.com/56kje26 originally displays awebpage titled “JoePrivatelnfo” (created from step 23A of FIG. 5). Usingthis embodiment of FIG. 7, Joe can change this file suffix to“79dfjk34”, and http://Joe.GM.com/79dfjk34 would then subsequentlydisplay the same identical webpage “JoePrivateInfo”, thereby achieving adegree of privacy control through pFD-URL change.

[0224] Notice that we could have also placed the password entry pointinstead at step 13 instead of step 15 and allowed the individual tochange his subdomain name. Though this is possible, it is not preferredfor sociological reasons, rather than technical reasons. Socially, it ispreferred that the individual not change his identity and organizationalaffiliation much (Oust as one would not change their birth name often).However, if password reentry is at step 13, technically this can happen.

[0225] In this embodiment, the redirection mechanism enables theredirector to quickly and easily change the URLv file suffix to anothername. This is done by remapping the file suffix. Because using theredirection mechanism does not have to comply with URL standard syntax,the redirection mechanism can be looser in syntax. But the pcsm stillshould check the layman's input. The layman user now has a SDpFS with adegree of privacy achieved through URL file suffix control—a VSApFS.

[0226] For the same reasons as explained in the section above that anVSAFS creates a type of ndfSDFD, in this section, the nVSApFS creates atype of ndtSDpFD.

Vd. pFD Embodiment Using Standard Subdomain and Redirector Database

[0227] Unlike the virtual subdomains above, the standard subdomain is asubdomain whose name is registered and recognized in the domain's DNStable. Standard subdomains are usually not changeable by layman usersbecause this typically requires giving the user access to DNS tables,which means that the layman can damage the domain's settings. Theprocess of adding and changing file suffixes is also usually notaccessible to layman users and instead is accessible to web programmersand administrators.

[0228] In this embodiment, as shown in FIG. 8, the subdomain name islisted in the domain's DNS subdomain table (11). This subdomain pointsto a sSDFSserver (the first “s” is forstandard—standard-Subdomain-Domain-File-Suffix-server) which parses theHTTP 1.1 sSDFS URL calls to determine the standard subdomain, domain,and file suffix names, and then maps the file suffix to the chosenaction script.

[0229]FIGS. 7 and 8's creation and change of their respective SDpFS aresimilar, both using action scripts with associated file suffixes to setup a redirection database (25). The initial differences are in steps 11and 14. In FIG. 8's step 11, the subdomain is in the domain's DNS tables(typically placed by an administrator instead of a user because of thecomplexity and security involved in DNS changes). In step 14, thesSDFSserverl checks to make sure that the user's entered subdomain anddomain have been registered before proceeding and then allowing for filesuffix entries.

[0230] For pcsm, FIG. 8's steps 15 a, 16 a, and 18 a shows how the usercan change his mapping of file suffix names to action scripts. First, alayman reenters at step 15 a with a password and enters a new file name.A pcsm check is made on the correct syntax (including URL syntax) ofthis new file name (16 a). If the URL syntax and other pcsm checks areaccepted, the process continues to step 16. If not, the user is asked tochoose another file suffix name at step 15. If accepted, thesSDFSserverl then maps (25) the second file suffix and eliminates theoriginal file suffix. The layman user now has a SDpFS with a degree ofprivacy achieved through URL file suffix control.

[0231]FIG. 9 (similar to FIG. 6) shows how this embodiment's SDpFS wouldbe displayed. After the DNS processing and forwarding (24) by thestandard subdomain, the URL call is parsed (25), and the sSDFSserverland the redirection database (27) then maps the file suffix to an actionscript (32, 33), and this action script call upon previously storeddatabase information (28, 29) to return through the Internet the SDpFSinformation.

[0232] Again, an SDpFS embodiment is shown, where a layman individualcan change the file suffix and retain his original web content, thususing URL file suffix changes to secure a degree of privacy. A nSDpFD isa subset of a SDpFS. And since this embodiment has a database field thatcan form “df's, this embodiment can also form a ndtSDpFD, andsubsequently ndfSDpFDA, the preferred nURLv.

Ve. pFD Embodiment (SDFD) with Standard File Directory FD, With StandardSubdomain, Without Redirector Database

[0233] When a browser issues a URL call without a file name in adirectory, then the web server typically returns a preset-named defaultfile, typically index.html, in the directory. Hence, if a browser made ahttp://call—“Joe.GM.com/cars” or “Joe.GM.com/cars/”,“Joe.GM.com/cars/index.html” is then displayed. If index.html is notwithin the “cars” directory, an error condition may result or directorystructure shown.

[0234] URLs with file names are longer and more difficult tocommunicate, particularly verbally, than URLs with only file directorynames. For example, “Name.Domain/Directory” is easier and shorter tocommunicate than “Name.Domain/Directory/FileName.html”. Furthermore, aURLv with FD/ is more difficult to communicate, particularly verbally,than a FD, which is why FD is preferred.

[0235] In the redirection URLv embodiments above, file suffixes can besolely file directories because these embodiments' redirection databasesallow for redirection of a file directory name to a specific file name.However, in order to use solely file directories in a standard,non-redirected file directory the default file should be within thedirectory

[0236] A redirector database allows for a SDpFS because the redirectionis changeable. A standard, non-redirected file directory is not easilylayman changeable, and cannot act by itself as a SDpFD. However, anadd-on process can allow for a standard file directory to change whilemaintaining the same content.

[0237]FIG. 10 (mostly derived from FIG. 8) shows this embodiment. Here,typically, the domain administrator adds the desired subdomain name tothe domain's DNS table and directs this subdomain to a hostingsSDFSserver2 (11). This sSDFSserver2 works differently than sSDFSserverlof FIG. 8. sSDFSserver2 sends a CGI form to the user, and the userenters the desired subdomain and domain. To form an initial SDFD, theuser then chooses a file directory name (15). User then chooses anaction script for the file directory (16), and then submits the form(17).

[0238] On step 18, the sSDFSserver2 analyzes the user requested SDFDdifferently than the above redirector embodiments' servers' analyses.Because sSDFSserver2 will create a file directory based on the filedirectory name, pcsm has to ensure that the user's requested filedirectory name will form appropriate web server and URL syntax.

[0239] After analyzing the user's proposed file directory and assuringit is URL-syntax and web server acceptable, the sSDFSserver2 then sendsan action-script-defined CGI form to the user (20A or B), that the usercompletes (21A or B), and from here, the sSDFSserver2 would create afile directory with the user-submitted file directory name and place anindex.html (default file) in this directory. The web content of thisindex.html is created by the user's selected action script's actions (19& 23A or 23B). Patent application Ser. No. 10/189,063 explains steps 19to 23 thoroughly, as can be seen in FIG. 5 (prior art).

[0240] To changes a FD name, the layman user can reenter with a passwordin through step 15A. The user then selects a second file directory name(15) and chooses the original action script (16). Pcsm URL and webserver check is made (18). In step (18A), the sSDFSserver2 detectswhether the action script had been previously used, and if so, thesSDFSserver2 creates the second file suffix directory (31) and movescontent from the original file suffix directory into the second (32),and erases or redirects the original file suffix directory (33).

[0241] Through the above embodiment, the layman user again gains amechanism to quickly establish a SDpFD and change his file directorywhile retaining the same content. Thus, the user gains a SDpFD withprivacy made through FD-URL control.

[0242] A nSDpFD is a subset of SDpFD. By creating the FD default filesas having data fields, a ndfSDpFD is formed.

Vf. pFS Embodiment of nSDFS, Without Redirector Database, and WithStandard Subdomain

[0243] This embodiment is similar to immediately above, except that thefile name is included in the file suffix. In this embodiment, for step15 of FIG. 10, the user is requested for file suffix that includes afile name, and this file name is used instead of index.html (defaultfile) in the file-suffix-named directory (23A & B). This embodiment isweak in verbal communications because it lengthens the URL, buttechnically it resembles the immediately above.

Vg. pFD Embodiment of Dynamic Web Database Creating Web Content Based onFile Suffix and File Directory

[0244] In these dynamic web database cases, a web database and webserver generally will parse the file suffix portion of a HTTP 1.1 URLcall that has a nSDFS or nSDFD, and use the parsed nSD and parsed FS orFD to cause a database action that generates and returns web contentspecific to the nSD and FS or FD. Each web database is designed andworks differently, and so the processes are different.

[0245] For changing the FD, the web database and server will eithergenerate the same web content for a second FD or remap the second FD tothe original web content. To change his FD, the layman user accesses aprivate entry to the area with the FD change module for the nSDinvolved. He then receives a form requesting the second FD name and theoriginal FD name or original web content generation process name. Hecompletes and submits the form to the web database. The web databasethen either remaps using the second FD to map to the original FD webcontent or regenerates the original web content using the second FD.Finally the database automatically deletes or remaps the original FD.Again, the pcsm needs to check the layman user for the viability of theURL formed.

[0246] Again, an SDpFD embodiment is explained, where a laymanindividual can change the file directory name and retain his originalweb content, thus using URL changes to secure a degree of privacy. AndfSDpFD is a subset of SDpFD. The data fields in the ndfSDpFDA will besupplied by the database.

Vh. pFD in SDpFD Embodiment—Without Redirector, WithoutWebpage-Creating-Database, With Standard Subdomain and With StandardFile Directory

[0247] In the above nURLv embodiments, a database generated the displaywebpage file (e.g. FIG. 7—23A & B) and placed it in the file directoryspecified by the user.

[0248] Though preferred, such a webpage-creating database is notrequired, as other mechanisms can place the display webpage file intothe file directory. For instance, an administrator can program awebpage-display file and move it into the original file suffixdirectory.

[0249]FIG. 11 shows a pcsm to create pFD working with this type ofnSDFD. The original webpage information with a default file name hasalready been placed into an addressable SDFD (11). The user enters apassword (12) to gain access into the file directory change process. Heenters in the original file directory name (13) and then enters thesecond file directory name (14). The pcsm checks the second filedirectory name for URL form (including URL syntax) (15). Once the secondfile directory name is accepted, the process then creates a newdirectory (16) with the second file directory name, moves (17) all filesfrom the original file directory to the second file directory and erases(18) (or redirects) the original file directory and files. A nSDpFD isformed by pcsm. By adding data fields to the original webpage content, andfSDpFD is formed.

Vi. Layman-Usable Criteria of Pcsm

[0250] Pcsm should be simple for a layman to use. UNIX and Lynx commandsto accomplish the above are usually error-prone because laymen areinvolved, and giving layman users access to a type command environmentis also error-prone. For example, requiring the users to recall and usea “ren” command would be unacceptable, because many laymen wouldincorrectly execute the command.

[0251] A graphical folders system for renaming file directories will beacceptable, provided that the users can have private access only totheir directories on the web server, be given directory names they areallowed to affect, and then be able to rename the directory name usingclick and rename, much like using a Microsoft Windows Explorer tool. Apcsm check still should be made. Checks should be made that the laymandoes not affect directory names or files that he or she should notaffect. The original FD's links in the ndfSDpFDA family can beautomatically renamed and linked to the second FD.

Vj. pFD Embodiments Using Other Techniques

[0252] As URL web content can be created using numerous other prior-artprogramming methods, it is difficult to enumerate all the cases wherepcsm can be used. The important factors are that the layman has aprivate browser access to his ndfSDpFDA FD change process, locate filedirectory names that can be changed, easily change the file directoryname, have the formed URL formed checked out for correctness, ensurethat the layman doesn't inappropriately affect files, server settings,DNS settings, ensure that the original FD doesn't display the originalcontent, and with the final result that the second FD displays theoriginal webpage content.

Vk. Automatically Replacing the FD Links in the nSDFDA Family

[0253] As mentioned above, when an original FD changes, pcsm can alsochange all the nSDFDA family members that had linked to the original FDto now having links to the second FD. Pcsm accomplishes this bysearching for the original nSDFD link in the nSDFDA family and replacingit with the second nSDFD.

VI. nSD With Public Communications Channel, Spam Control, and PublicEncryption

[0254] An individual representation system should have a way of publiccommunications. Many people use SMTP and POP email with the publicaddressing syntax of “name@adomain.com” for their means of publicInternet communications. However, such email systems are being inundatedwith email spam. An Internet-based individual identity andrepresentation system, as this invention is, should have aspam-resistant email system.

[0255] A preferred component of this invention is that a http://nSDprovides a public channel of communications to the individual. Forexample, http://Joe.GM.com has a webpage-user-input-box for emailcommunications (a webpage form email), as can be seen on FIG. 4, item(7). An advantage of using http://nSD to include the public channel ofcommunications is that the nSD syntax resembles the popularname(,adomain.com SMTP email addressing syntax. When an individualissues his communications channel by using his nSD, (whether issuedusing a paper business card, verbally or through the Internet), there isless explanation required by the issuer as to the novelty or usage ofthis web based contact method. For example, Chen.WebAndNet.com is verysimilar to Chen@WebAndNet.com.

[0256] This public channel of communications at nSD is also valuable tothe ndfSDpFDA family in as follows. As seen above, Joe of GM.com hasnumerous profiles, and his FDs can change and be eliminated; forexample, Joe.GM.com/sedans can be changed to Joe.GM.com/Chevysedans, andJoe.GM.com/sedans be eliminated. To locate Joe's sedans again, aJoe.GM.com/sedans inquirer can http address Joe.GM.com to webpage-formemail Joe to request the new ndfSDpFDA for Joe's sedans. Likewise, ifJoe.GM.com/56kje26 was changed, his prior special customers can contactthrough Joe.GM.com's webpage-form email, and ask Joe for where thespecial deals link is.

[0257] The http://nSD's web content for spam-resistant publiccommunications channel can include telephone number, postal addresses,and Internet-based spam-resistant techniques, such as an user's readingand confirming graphically generated word images before receivingclearance to submit form email. However, spam-prone name@adomain.comemail address syntax should be avoided on this nSD, unless the“name@adomain.com” email address accompanies spam-resistant controls.

[0258] Perhaps the easiest spam-resistant communication channel is touse webpage-form email that forwards the message to the namedIndividual. Webpage-form email is as its name describes—an example beinga webpage's rectangular user-type-input-form boxes in which the typedcontent is then forwarded, seen commonly on the “Contact Us” webpage ofdomain websites. The sender calls up the URL with the webpage-formemail, types his message in the input-box, perhaps clicks a fewcheckboxes associated with the webpage's questions, and clicks a“submit” or “send” button. The message is then sent to the web server,which processes URL call and its email message, and then forwards themessage to the intended recipient. Other examples of webpage form emailare rectangular-user-input-boxes of browser-outbound-mail such as inYahoo! Mail. Frequently, webpage-form email has additional required forminputs, such as clicking check boxes, putting in reply email address,and/or pull down options in drop-down-menu boxes. The message and anyadditional user inputs are then sent for web server processing thatsubsequently forwards the message to the intended recipient. This isprior art, and a sample of one is seen in FIG. 4 (3 & 7).

[0259] Webpage-form email can be spam resistant because simple changescan be made to its form resulting such that sending spam becomeseconomically more expensive. For example, domain A's webpage form emailfor its individuals may require that 2 check boxes be checked off beforeforwarding the mail. Domain B may check that a legitimate reply emailaddress (one that doesn't bounce back after sending) be filled in a formbox before forwarding the message to the recipient. Domain C may requirethe user reading and entry of a graphical image containing text beforeaccepting the form email. Domain D may require 3 check boxes. Thespammer can obviously circumvent each of these various barriers;however, his economics of sending the spam increase exponentially as heencounters many different domains with differing webpage form-basedemail reception requirements for the domains' individuals.

[0260] Email spamming using namegadomain.com addressing syntax is lowcost because it is easy and fast to send out bulk email to millions ofdifferently addressed name@adomain.com syntax addresses. To send to eachwebpage form email, the spammer has to pull in each individual's URL,wait for it to download, and then complete and submit each webpage-formemail with its additional required user inputs. The spammer's problem isthese webpage-form email processes are very slow and resource consumingactivities (compared to bulk-mail addressing using the popularname@adomain.com syntax)significantly raising the bandwidth costs of thespammer. Also, because it is slow, the spammer can be quickly detected.

[0261] Yet, the speed of webpage-form email download and send is verysuitable for humans to personally type and send emails. Since the nSD'sweb content can contain webpage form email, and nSD can be easilyverbally communicated and resembles name@adomain.com syntax, the nSD canalso serve well as the spam-resistant public communications systemaddress.

[0262] As email is frequently used, it will be valuable that thepreferred public communications channel address (nSD) be quickly createdfor use. Standard subdomains are slow to create and suffer from DNSpropagation delays. Virtual subdomains can be created quickly and don'tsuffer from DNS propagation delays, as explained in U.S. Pat. No.6,442,602 by Azkar Choudhry, and patent applications Ser. Nos.09/642,127 and 09/853,167 by Chen Sun and Azkar Choudhry. Patentapplication Ser. No. 09/853,167 also shows how business card format webcontent can be database generated for addressed nSDs. Prior-artprogramming routines can add a webpage form email on each of thesevirtual subdomain nSD webpages with additional checkboxes and thuscreates a spam-resistant public communications channel and web addressfor the ndfSDpFDA family.

[0263] Additionally, http://nSD may include a downloadable publicencryption key, providing a convenient and easy-to-remember address andmethod to attain the key for data encryption.

VII. Searchable Index of nSDs With Spam Control Public CommunicationChannel

[0264] Present website means of displaying an organization's personneland contact method is typically listing on a webpage the person's nameand title, and including their namegadomain.com syntax email address.Web robots can read these web pages and collect email addresses with thesyntax name@adomain.com from these webpages, enabling spammers toconduct bulk mailings.

[0265] As explained in patent application Ser. No. 09/853,167, virtualsubdomains can also form a searchable index of nSDs. Likewise, we cansee from the database designs in FIGS. 5, 7, 8, 9, 10, and 12 as well asin patent application Ser. No. 10/189,063 by Chen Sun, that databasegenerated webpages of nSDFDAs can be formed. These nSDFDA databasescontain the web content of nSD and ndfSDpFDA. Using their query andsearch capabilities, these web databases can also form searchableindexes of ndfSDs' and ndtSDpFDAs' web content. For example, people'snames, titles, job functions, locations, and other ndfSDpFDA content canbe searched. Patent applications Ser. Nos. 09/853,167 and 10/189,063additionally show how such an index can form a searchable personneldirectory for the domain's associated individuals.

[0266] In the present invention, the nSDs of such searchable ndfSDpFDAindexes contain section VI's public communications channel, so when theindividual is searched for and found, the user can communicate with thisindividual, though this public communications channel. This channel isfrequently a webpage form email. For example, users can quickly findsomeone in an organization by searching a web index of theorganization's domain-name-associated-personnel (index of ndfSDpFDAs),pull up the personnel individual's nSD webpage, and then use theindividual's nSD's spam-resistant webpage form email to contact him. Theeffect will be a searchable, communicable web index of a group of peopleassociated with a domain.

VIII. IWeb and ndfSDpFDA Overview

[0267]FIG. 12 is a second overview of the invention's overall systemdesign. It first uses a ndfSDpFDA family (3) which is comprised of andfSD (1), and ndfSDpFDs (2). The ndfSDpFDA can enter into IWebs (4),which use arid manipulate the data fields of the http://ndfSDpFDA toconduct Individual exchanges processes. The IWebs use the text of thenSD as the individual identity (5). Various IWebs can consolidate theircollected information on a nSD-text-as-identity to form brandingcharacteristics for individuals and domains (6).

[0268] A hWeb is a prior-art type of website where individuals exchangeand share information with other individuals and this information maylead to other kinds of exchanging. Examples of hWeb software include thesoftware for eBAY.com, Matchmaker.com, employment websites, and UltimateBulletin board discussion forum, which are all known prior arts. Theindividuals' representations in hWeb software sites include web handlenames, email addresses, and account names.

[0269] IWeb are individual exchange software and sites in which itsindividuals' representation is a nURLv, preferably ndfSDpFDA. And, asexplained in the data communications section above, an IWeb can searchon and extract the web content of an addressed ndfsDpFDA. We'll showbelow how ndfSDpFDA, being IWeb's preferred individual representation,offers advantages over the individual representation forms in hWebsoftware and sites.

IX. IWeb & ndfSDpFDA Embodiment: Contact Manager, IWebContacts

[0270] In this section, we will show an IWeb-ndfSDpFDA interaction andembodiment—a contact manager called IWebContacts.

IXa. History of Contacts Managers

[0271] Contacts management deals with the storage and retrieval ofpeople's contacts information. Historically, business card holders andaddress books served this purpose. The onset of computers brought forthdatabases specifically designed for contacts management, such as ACT,which can be acquired from Symantec Corp., Outlook from Microsoft, andGoldmine from FrontRange Solutions. These non-web-based contactsmanagers typically contain fields including individual's name, somemethod of contacting the individual, such as his/her address, telephonenumber, fax number, the organization he/she represents, and title. Otherdata fields can include associated office personnel (e.g. assistant'sname), birthday, communications activities with the individual, plan ofaction, digital certificates, IDs, billing information, attachments,hobbies, fields suitable for specific industries, and user definedfields. These non-web-based computer contacts managers automate many ofthe search and retrieval functions over using paper-based business cardsand indexes.

[0272] The entry, exchange, update, and graphics requirements ofcontacts information remain cumbersome for these non-web-based computercontacts managers. The contacts information received by the recipient donot automatically update when the sender's contacts information changes(dynamic updating); entry is typically accomplished by typing; cardscanners are time-consuming, inaccurate, and costly; graphics aredifficult to handle.

[0273] Furthermore a non-web-based computer contacts manager's channelsof communications and exchange are usually limited to a few—e.g. onlydata communications. Channels of contacts information communications andexchange can include data communications, email, face-to-face oral,telephony, data import/export, handwriting, and print exchanges.

[0274] vCard (from Internet Mail Consortium) a standard using datacommunications for relaying information among non-web-based contactsmanagers lacks verbal and written exchange capabilities, wide andextensive usage, extensive graphics, and dynamic updating.

[0275] As a result, most contacts information exchange continues to berelayed by telephone (verbally), postal mail (paper business card), orface-to-face exchange (paper business card), and the collected contactsinformation are then manually typed into a non-web-based contactsmanager.

[0276] Web-based contacts managers have graphical contacts informationand dynamic updating, with websites such as Netscape's Net BusinessCard. In these, the representation of an individual contacts is using acomplicated file suffix in the respective website's domain name and theindividual's name is behind the domain name. For example, suppose JohnSmith of Ford Motors (Ford.com) wanted to use a Netscape card. He wouldreceive an URL like Netscape.com/˜d35k/256/JohnSmith, a URL that FordMotors is unlikely to approve of. Other web-based contacts managerwebsites require an individual to use the contacts manager's domain nameplus using assigned codes.

[0277] U.S. Pat. No. 6,442,602 and patent applications Ser. Nos.09/642,127, and 09/853,167, filed by Chen Sun and Azkar Choudhry, showedhow to build sets of web business cards with people's names in front ofan associated domain name, using a technology called virtual subdomainaddresses. For example, in the URL JohnSmith.Ford.com, “JohnSmith” isthe subdomain name and Ford.com is the domain name.

[0278] These patent and patent applications also contained the computerprogram code to add web business cards to any number domain name. Moreimportantly, the applications explained how any domain name can use aremote server (for example, one administered by an outside service) toadd such subdomains to an existing domain name. Hence, Ford.com andUSPTO.gov can easily provide all its employees virtual subdomain address(VSA) business cards, using the technologies described in theabove-mentioned patent applications.

[0279] Patent application Ser. No. 10/074,081 “Contacts Management UsingVirtual Subdomains” by Chen Sun explains a contacts manager inventionthat utilizes virtual subdomains coupled to domain names. Here a contactmanager is built using individuals' identities having the syntax“Name.Domain” and using http://nSD addressing of this syntax to search,store, and retrieve individuals' contacts data.

[0280] People though desire privacy. A Name.Domain combination placedinto a contacts manager lacks a degree of privacy, as all webinformation of the named individual is easily public, once the person'sname and his organization's domain are known. There thus arises a needfor a contacts manager that can utilize nURL addressing and canaccommodate a person's privacy needs.

IXb. Sample Data Used in the Contacts Manager

[0281] To explain this IWeb embodiment, eight ndfSDpFDAs with associatedcontacts data are listed in Table 1. In prior-art contact managers, asingle individual typically has a single URLv field, usually for theindividual's organization's www.adomain.com's URL. However, as can beseen in Table 1, an IWeb contact manager has to accommodate severalnURLv profiles per individual. TABLE 1 Examples of ndfSDpFDAs withAssociated Contacts data Contacts Contacts Contacts Contacts Contactsdata data data data Information Stored ndfSDoFDA (nURLv) OrganizationFirst Name Last Name Occupation Contact BobJones.CompanyA.com Company ABob Jones Employee browser mail form BobJones.ComoanyA.com/biz Company ABob Jones Accountant bob@companya.com BobJones.CompanyA.com/fun CompanyA Bob Jones Golf bob@personalmail.com Mary.CompanyA.com Company A MaryJones Lawyer Telephone number Bob.FirmB.com Firm B Robert JohnsonPartner Browser mail form Bob.FirmB.com/accountant Firm B Bob JohnsonAccountant bob@firmB.com Bob.OrganizationC.org Organization C Bob RothPreacher Tele Bob.OrganizationC.org/life Organization C Bob RothBob@organizationC.org

IXc. Prioritization and Consolidation of ndfSDpFDA Data FieldInformation in IWeb

[0282] Understand that IWeb, as it is capable of using multiple profilesof an individual, would sometimes receive different information on thesame data field of the same individual. Notice in Table 1 thatBob.FirmB.com has “Robert” in the first-name data field andBob.FirmB.comn/accountant, has “Bob” in the first-name data field,though these are the same individual. In order to data manipulate,store, and present data field information efficiently, the IWeb actionshould give higher priority to one profile's name. In this sample case,if Bob.FirmB.com has priority over Bob.FirmB.com/fun, “Robert” will havepriority over “Bob”.

[0283] An IWeb can also consolidate the various redundant information,again to save storage space, expedite processing, and facilitate user'sease of viewing. Table 2 shows the result of an IWeb action that hasextracted from Table 1 data fields—Organization, First name, Last name,and ndfSDpFDA names—and prioritized and consolidated the redundantextracted field information. Notice that it is easier to read, shorter,and saves storage space. TABLE 2 Extracted ndfSDpFDA prioritized andconsolidated Contacts Contacts Contacts data data data OrganizationFirst Name Last Name Stored ndfSDpFDA Company A Bob JonesBobJones.CompanyA.com, BobJones.CompanyA.com/biz,BobJones.CompanyA.com/fun Company A Mary Jones Mary.CompanyA.com Firm BRobert Johnson Bob.FirmB.com, Bob.FirmB.com/accountant Organization BobRoth Bob.OrganizationC.org C Bob.OrganizationC.org/life

[0284] The IWeb can, of course, have the redundant informationunconsolidated, in which case, each ndfSDpFDA would be a databaserecord. In the consolidated form, each individual may have severalndfSDpFDAs. Tables 1, 6, and 8 are unconsolidated, and Table 2 isextracted, prioritized, and consolidated. These consolidation andprioritization actions are accomplished by the database accompanyingndfSDpFDAs and its associated contacts data.

[0285] Note that the user's viewer for the IWeb will differ greatlywhether unconsolidated (Table 1) or consolidated (Table 2) views arebeing offered. If the consolidated view is offered, this will resembleprior art contact managers (e.g. Outlook or ACT), except that it hasnumerous ndfSDpFDA fields (which can be hyperlinked) and the prior artcontacts managers usually have only one such field, for itsorganization's domain URL. The IWeb's viewer can also incorporate aseparate domain URL field.

IXc. Computing Equipment Used

[0286] In section IX's as well as in most other sections, the webservers are preferably Apache Web servers and the personal computerclients are running Microsoft Windows 2000 connected to the Internet andusing Microsoft's Internet Explorer.

IXd. IWebContacts Components

[0287] IWebContacts components consists of the search and extractionfacility, the database of ndfSDpFDAs with any associated and extractedcontacts information of the ndfSDpFDAs, computing services to manipulatethe database including fore-mentioned consolidation and prioritizationservices, any services that generate the query forms being sent, and anyweb or platform services to operate the above. The noted hash marks ofFIGS. 13-19 show several IWeb components.

[0288] IWebContacts, the name of the IWeb contacts manager embodiment,has two types. Type 1 stores ndfSDpFDAs as text records and does notstore other ndfSDpFDAs' contacts data. Type 2 stores ndfSDpFDAs anddownloaded ndfSDpFDAs' contacts data. Each type has several embodiments.

IXe. IWebContacts, Type 1—Stores ndfSDpFDA Without ndfSDpFDA'sAssociated Contacts Data

[0289]FIG. 13 shows the invention-embodiment, an IWebContacts type 1.This IWebContacts has a database of user's stored ndfSDpFDAs, querysearch form, and search facility that can search the Internet for thendfSDpFDAs' associated contacts data.

[0290] To illustrate Type 1, the user starts with the first sevenndfSDpFDAs of Table 1 in his ndfSDpFDAs database (40). He adds (40 a) andfSDpFDA by typing in Bob.OrganizationC.org/life into his database. Ofcourse, he can delete (40 b) any of the ndfSDpFDAs.

[0291] To search, user receives a query search form (41) with searchfields. In this example, the search fields include “Organization”,“First Name”, “Last Name”, “Occupation”, and “Contact”. Other querysearch forms may have different search fields. The user searches for“Accountant” in the “Occupation” field. (Table 3). TABLE 3 Sample QuerySearch Form, Search Fields, and “Occupation” Search First Last QueryOrganization Name Name Occupation Contact Accountant

[0292] A search facility would then extract (B & C) the text of theuser's stored ndfsDpFDAs (40) and form URLs (43), one way by simplyattaching http:// in front of any of the stored ndfSDpFDAs.IWebContacts' search facility then uses http://ndfSDpFDA to address (D)the Internet (44) and access a ndfSDpFDAserver. CompanyA.com is servicedby ndfSDpFDAserver A (45 a); FirmB.com, ndfSDpFDAserver B (45B); andOrganizationC.org, ndfSDpFDAserver C (45C). These would respond with theweb contents of the ndfSDpFDAs, as in the data in Table 1.

[0293] Upon receiving the response (46 a), the user's search facilitythen parses it (46 b) and determines whether the response contacts datameet the search criteria (46 c). It deletes any non-matched ndfSDpFDAsand deletes any unnecessary fields' information (46 d) in thesendfSDpFDAs. Then it sends results to user's display (47 a), which candisplay a list of matching ndfSDpFDAs and/or their associated contactsdata (47 b).

[0294] In this example, when searching for “Accountant”, user receivesBobJones.CompanyA.com/biz and Bob.FirmB.com/accountant (and/or theirassociated contacts data) (Tables 4& 5) TABLE 4 Results Displayed onBrowser as ndfSDpFDAs BobJones.CompanyA.com/biz Bob.FirmB.com/accountant

[0295] TABLE 5 Results Displayed on Browser as ndfSDpFDAs withassociated contacts data. BobJones.CompanyA.com/biz Company A Bob JonesAccountant bob@companya.com Bob.FirmB.com/accountant Firm B Bob JohnsonAccountant bob@firmB.com

[0296] Major varieties of Type 1 are described below. The differencesamong these involve the questions: 1. are ndfSDpFDAs stored—local to theuser or accessed online, 2. will it be a single or severalndfSDpFDAserver hosts handling the ndfSDpFDAs, 3. is the search facilitywithin or independent of the ndfSDpFDAserver, and 4. how is thecommunications transferred between IWebContacts search facility andndfSDpFDAservers?

[0297] These differences are important factors because where thendfSDpFDAs are stored and processed greatly affect the speed and typesof computing devices. For example a diskless web client or a palmtop maynot effectively store contacts information locally. How the ndfSDpFDAscontacts data is data communicated also greatly affect the speed and theease of programming, particularly since http is a stateless protocolgoing over remote data lines.

A. Embodiment A of Type 1—ndfSDpFDAs online (FIG. 14)

[0298] In this embodiment, the user's ndfSDpFDAs (50) are stored on aweb database (51) that the user has password access to. Both the webserver and personal computer (54) are connected to the Internet.IWebContacts (55) contain ndfSDpFDA database, search facility, and webservices.

[0299] The user uses a browser (54) to Internet access (A) his webndfSDpFDA database. The IWebContacts (55) responds (B) by sending adisplay of the user's stored ndfSDpFDAs as URL links in his browser. Theuser can select a ndfSDpFDA-URL link to see full contacts data, or hecan search on these ndfSDpFDAs.

[0300] Should the user searches (C), the IWebContacts (55) responds (D)with a web form with contacts data fields for searching (Table 4). Usinghis keyboard, the user inputs the search criteria, and submits (E) theform. The IWebContacts receives this search request, reads each of theuser's stored ndfSDpFDAs (50), and Internet addresses (F) usinghttp://ndfSDpFDA. The appropriate ndfSDpFDAserver (45 a, 45 b, or 45 c)responds (G) with the ndfSDpFDA's contacts data. The IWebContacts searchfacility (52) parses and searches this contacts data to determinewhether it meets the search criteria. IWebContacts then sends (H)matching ndfSDpFDAs and relevant associated contacts data to the user'spersonal computer as a list. The user can then further click (I) anyreceived ndfSDpFDAs to activate the hyperlink that enables him to see(J) the ndfSDpFDA's associated contacts data on his browser.

[0301] Query search data communications standards will be set betweenIWebContacts' search facility and the ndfSDpFDAserver. This isaccomplished by one of the various data communications methodsabove—HTML commentaries, XML, and others.

B. Embodiment B of Type 1—ndfSDpFDAs Local (FIG. 15)

[0302] In a second embodiment of type 1, as shown in FIG. 15, the user'sndfSDpFDAs are located in a searchable database (60) on his personalcomputer or other local computing devices (61), instead of on a webserver. There are three ndfSDpFDAservers in FIG. 15, one forCompanyA.com, one for CompanyB.com, one for OrganizationC.org, allconnected to the Internet.

[0303] When the user uses the query search form (Table 3) (63), thesearch facility (62) would extract the personal computer's database'sndfSDpFDAs (60), create a ndfSDpFDA-URL (http://ndfSDpFDA), and addresstheir ndfSDpFDAservers. The ndfSDpFDAservers would return ndfSDpFDAs'contacts data and search facility would determine which meet the searchcriteria. The results would then be displayed on a browser (Table 4 and5) (64).

Embodiment C of Type 1: ndfSDpFDAserver Host With Multiple Domain Names

[0304] In this embodiment, the ndfSDpFDAservers are located on a singlehost computing facility, instead of being located on different hostcomputers or servers. This can be accomplished through setting thestandard subdomains at different domains to be directed to the singlehost. Upon receiving the ndfSDpFDAs-URL call, the single-hostndfSDpFDAserver can parse the request to determine the ndfSDpFDA'ssubdomain, domain, and file directory and send back the appropriatendtSDpFDA's web content. As an illustration, ndfSDpFDAservers 45 a, 45b, and 45 c of FIG. 15 would be all consolidated into at a single hostserver.

[0305] A certain type of SDFDAserver is well suited for this purpose,the VSAFSserver designed in patent application Ser. No. 10,189,063,“Virtual Subdomain Address File Suffix”, by Chen Sun. FIG. 16, which isFIG. 7 from Ser. No. 10,189,063, shows a VSAFSserver. This type ofserver is easy to implement, because the various ndfSDpFDAs' domainswill simply have to place a single redirector device in their DNS tablefor the subdomains, and the VSAFSserver can take care of providing webcontacts content from a single server.

[0306] If the search facility is also on the single-hostndfSDpFDAserver, the searches would be significantly faster, as much ofthe searching takes place on a single host computer, rather thanmultiple accesses through the Internet. Unlike http, which is astateless protocol that is more difficult for programmers to programcontacts data located on remote and scattered hosts; now, theprogrammers can more easily program the different domains' contactsdata, as these are all centrally accessible. And, if the user's onlinendfSDpFDAs were also on the same host, speed again would be greatlyexpedited.

IXf. IWebContacts Type 2—ndfSDpFDAs and Associated Downloaded ContactsData are Stored

[0307]FIG. 17 shows a second type of IWebContacts. This IWebContactstype has its own searchable database (83) where each record includes andfSDpFDA field and selected fields of the ndfSDpFDA's associatedcontacts data. The selected fields of contacts data are previously set(80). A user first populates his IWebContacts' database (83) by adding(81) and deleting (82) ndfSDpFDAs into the database's ndfSDpFDA field.The search facility (84) acquires (A) the newly added ndfSDpFDAs namesfrom the database, adds “http://” to the ndfSDpFDAs to form URLs,Internet addresses (B) the ndfSDpFDA-URLs, and receives (C) theassociated contacts data from the ndfSDpFDAservers (45 a, 45 b, 45 c).The search facility then extracts the selected fields' data and saves(D) the data into the database (83). The data communications of fieldsinformation between the search facility and ndfSDpFDAservers isaccomplished by HTML commentaries, XML, vCard format, and other methodspreviously described.

[0308] In having its own local database, IWebContacts type 2 can usuallysearch much faster than an Internet access search to a ndfSDpFDAserver,as required in type 1.

[0309] For example, user's database and search facility have “FirstName”, “Last Name”, and “Company” as selected contacts data fields. Theowner of IWebContacts previously set these fields (80). The user enters(81) all the ndfSDpFDAs of Table 1 into the database. The searchfacility (84) retrieves (A) the newly stored ndfSDpFDAs, uses thendfSDpFDAs to address (B) the Internet and ndfSDpFDAservers and receives(C) the ndfSDpFDAs' contacts data. The search facility extracts datafrom the ndfSDpFDAs' First, Last, and Company Name fields and saves (D)these into a database's record along with their associated ndfSDpFDA.Using the ndfSDpFDAs of Table 1, the stored information in thisIWebContacts database (83) is as in Table 6. TABLE 6 IWebContacts'ndfSDpFDAs with selected contacts data fields' data Contacts ContactsContacts data data data Stored ndfSDpFDA Organization First Name LastName BobJones.CompanyA.com Company A Bob Jones BobJones.CompanyA.com/bizCompany A Bob Jones BobJones.CompanyA.com/fun Company A Bob JonesMary.CompanyA.com Company A Mary Jones Bob.FirmB.com Firm B RobertJohnson Bob.FirmB.com/accountant Firm B Bob JohnsonBob.OrganizationC.org Organization Bob Roth C Bob.OrganizationC.org/lifeOrganization Bob Roth C

[0310] Now, a query search (85) for “CompanyA” would search (E) locally(F) and display Bob.CompanyA.com, Bob.CompanyA.com/fun,Bob.CompanyA.com/biz and Mary.CompanyA.com (G) faster than through asearch accessed through the Internet (as in IWebContacts type 1). Tables7 and 8 shows this IWebContacts type 2 search TABLE 7 Query search formFirst Last Name Name Company Company A

[0311] TABLE 8 Search Results of IWebContacts type 2 with ndfSDpFDAslocal Organization First Name Last Name BobJones.CompanyA.com Company ABob Jones BobJones.CompanyA.com/biz Company A Bob JonesBobJones.CompanyA.com/fun Company A Bob Jones Mary.CompanyA.com CompanyA Mary Jones

[0312] When using the priority and consolidation mechanism, the visualresult would be rearranged, appearing as in Table 9, which resemblesprior-art contacts manager, except that several ndfSDpFDA fields arealso shown. TABLE 9 Search Results of IWebContacts type 2 withndfSDpFDAs local, using prioritization and with different visual viewOrganization First Name Last Name ndfSDpFDA Company A Bob JonesBobJones.CompanyA.com, BobJones.CompanyA.com/bizBobJones.CompanyA.com/fun Company A Mary Jones Mary.CompanyA.com

Embodiment A of IWebContacts Type 2 —ndfSDpFDAs local (FIG. 18)

[0313] In this embodiment, an IWebContacts type 2's ndfSDpFDAs' database(83), search facility (84), query form (85), and add and deletendfSDpFDA function boxes (81 & 82) reside on a user's personal computeror other local computing device.

[0314] The user enters (81) ndfSDpFDAs into the ndfSDpFDAs' database(83), and search facility (84) then addresses (B) the Internet usingthese ndfSDpFDAs and downloads (C) the ndfSDpFDAs' associated contactsdata.

[0315] Unlike the type 1 embodiments, the search facility (84) nextextracts the data from selected fields of the downloaded contacts data.Then the data is saved (D) into the respective IWebContacts databasefields (83) along with their respective ndfSDpFDAs. Query form (85) canthen search (E,F) the ndfSDpFDAs' selected contacts data, withoutrequiring Internet access.

[0316] IWebContacts can add computing routines to regularly Internetupdate its contacts database using current, on-line ndfSDpFDA contactsdata.

Embodiment B of IWebContacts Type 2 With ndfSDDFDAs Online (FIG. 19)

[0317] In this embodiment of type 2, the IwebContacts' ndfSDpFDAs andits selected contacts data are online and the user sees his ndfSDpFDAsas URL links in his browser, as shown in FIG. 19.

[0318] When he accesses his IWebContacts type 2 online, the userreceives from the IWebContacts (109) access to his database of storedndfSDpFDAs with selected contacts fields and data (83). He also receiveson his browser a enter data box, sent by IWebContacts, where he can “AddndfSDpFDA” (81). He enters and submits (R) his ndfSDpFDAs, andIWebContacts stores (R) these into the database.

[0319] As previously described for FIGS. 17 and 18, the search facility(84) uses (A) these ndfSDpFDAs as Internet URL addresses (by prefixinghttp://) and requests (B) ndfSDpFDAs' associated contacts data from thendfSDpFDAservers (45 a, 45 b, 45 c). The search facility can select datafrom specified contacts data fields. The ndfSDpFDAservers respond (C)with contacts data, and the search facility removes non-searched fieldsand data. The search facility then saves (D) selected contacts data andtheir respective ndfSDpFDA into the database (83).

[0320] When the user wishes to search his database, the IWebContactssends (S) his browser a query search form (85), and he inputs. The querysearch form is then transmitted (E) to search facility (84), which thensearches (F) his database (83). Search results consisting of selectedndfSDpFDA contacts data and respective ndfSDpFDAs are returned (G) tothe local computing facility. Using this embodiment, the user then cansearch faster than having to access the Internet and contacting eachdomain's ndfSDpFDAservers for contacts data.

[0321] For example, using a browser, user accesses the websitecontaining his ndfSDpFDAs, and receives “add ndfSDpFDA” box entry (81)sent by the IWebContacts. The user submits (R) ndfSDpFDAs of all thendfSDpFDAs in Table 1. IWebContacts receives and adds these into thedatabase (83).

[0322] Then, the search facility (84) extracts (A) and prefaces http://to these ndfSDpFDAs to use to address (B) their respectivendfSDpFDAservers (45 a, 45 b, 45 c). The ndfSDpFDAservers respond (C)with the information in Table 1. The search facility extracts the FirstName, Last Name, and Company fields' data, discards the remaining fieldsand data, and saves the extracted fields data into the database (83)with their ndfSDpFDAs, as in Table 6.

[0323] To prioritize and consolidate, results in Table 10. TABLE 10ndfSDpFDAs' selected contact fields' data are prioritized, consolidated,and stored Contacts Contacts Contacts data data data Stored ndfSDpFDAOrganization First Name Last Name BobJones.CompanyA.com, Company A BobJones BobJones.CompanyA.com/biz BobJones.CompanyA.com/funMary.CompanyA.com Company A Mary Jones Bob.FirmB.com Firm B RobertJohnson Bob.FirmB.com/accountant Bob.OrganizationC.org Organization BobRoth Bob.OrganizationC.org/life C

[0324] When the user wishes to search his database, the IWebContactssends (S) him a query search form (85), and, in this example, hespecifies “CompanyA” in the Company field. The form is returned (E) toIWebContacts, which then searches (F) its database (83). The results inTable 9 are returned (G) to the user.

IXf. Minor Differences in Using the “p” Privacy Module

[0325] The IWebContacts could not detect the usage of the privacy modulein the ndfSDpFDA, so for IWebContacts, it could operate nearly as wellusing ndfSDFDAs instead. A few minor issues can occur and are resolvedas follows.

[0326] a. This IWebContacts differs from a prior art contacts manager inthat the owner of the ndfSDpFDA can easily change its URL address bychanging its FD. IWebContacts then cannot download information. WithType 1 embodiments, all associated contacts information is lost. WithType 2, old information is stored.

[0327] b. In the event of a changed FD, the IWebContacts owner canpublicly communicate with the nSD to request for a revised URLv.

IXg. Advantages of IWebContacts

[0328] IWebContacts using ndfSDpFDAs illustrates a number of valuablebenefits both as a contacts manager invention-embodiment as well as anIWeb invention-embodiment.

[0329] 1. The issuer of the ndfSDpFDA can easily communicate his SD andprivacy controlled SDFD to another individual through verbal, written,and data communications of a easy-to-communicate nSDFDA syntax. This isunlike long talking of contacts information over the phone (e.g., fromissuer to each recipient, “My name is spelled . . . , I work for . . . ,my telephone number is . . . , You can contact me at . . . , my mailingaddress is . . . Let me find a piece of paper to write down all this foryou. I'll send you my card through postal mail.)

[0330] 2. The recipient simply types in a brief ndfSDpFDA, and thisinformation is now storable and capable of being data processingmanipulated. Compare this with having to type for minutes contactsinformation just to capture Name, Company, Address, etc. of a businesscard,

[0331] 3. The organization affiliated with the issuer (the individual)has a vested positive interest, as its organization receives promotionalbenefits of its domain name, while the issuer is promoting himself. Thisis accomplished by having the organization's domain name beingassociated with the individual.

[0332] 4. Unlike previous web contacts management technologies, theIWebContacts can accept contacts entities using multiple subdomains,multiple domain names, and with file suffix profiles. This enables for asingle contacts manager to receive and manipulate profiles informationfrom any number of domain names.

[0333] 5. The IWebContacts can receive multiple privately profiledinformation from an individual and consolidate these to form a morecomprehensive view of the individual.

[0334] 6. The issuer can efficiently reuse his ndtSDpFDA with manyIWebContacts. This can be through verbal communications, emailtransmission, handing over a piece of paper, and more. This issuer savestime.

[0335] 7. The recipient can enter a nSDFDA into his contacts managementsystem in less than 15 seconds and receive hundreds times moreinformation than having to take several minutes to type in business cardinformation.

[0336] 8. It's no longer necessary to send an email with a vCard after atelephone conversation, as the issuer can on the phone simply verballyissue his nSDFDA, and the recipient can enter this when convenient.Also, recipients are frequently unwilling to reveal their emailaddresses and can't utilize vCard.

[0337] In short, by using ndfSDpFDAs together with an IWeb, thisprovides magnitudes of timesavings for the issuer as well as therecipient. No prior art has accomplished this. Patent application Ser.No. 10/074,081 invention (also by Chen Sun) contact manager lacked theprivacy control and several profiles per individual features. Otherprior web based contact management websites used a singular domain name,file suffix holding individual's names, singular profile,difficult-to-speak individual URL representation, additional codingsystems, web handles, and other weakness. Other prior art, non-webcontacts management system did not have dynamic updating of contactsinformation, required extensive typing to enter contacts data, did nothave profiles of individuals tied into URLvs, and suffered many otherweaknesses. A novel, non-obvious solution and significant businessproductivity improvement resulted from using ndfSDpFDA together withIWebs.

X. Other Embodiments—Developing an IWeb by Starting From a hWeb and itsImmediate Resulting Differences

[0338] Many IWebs can be designed by starting with prior arts softwaredesigns similar to hWebs' software in websites such as eBAY.com,Matchmaker.com, Ultimate Bulletin board discussion forum, HotJobs.com,online chats, and others, which are known arts of websites in eCommerce,dating, discussion forums, employment, online chats, and others. Thoughthere may be tremendous varieties, all such hWeb sites deal with anindividual's entity conducting exchanges and have an individual'sentity's representation shown within the website. In the majority ofthese hWebs, a web handle is the individual's identity andrepresentation. An IWeb usually can distinguish between identity andrepresentation, as explained in sections XII and XIII below.

[0339] Programming changes that can be made to hWeb software to makethese an IWeb include:

[0340] 1. The web handle or other method of individual identification(e.g. email address) is replaced with a nURLv, preferably ndfSDpFDA.

[0341] 2. The ndfSDpFDA used can be hyperlinked to http://ndfSDpFDA.

[0342] 3. The hWeb be modified to use multiple web handles to representa single individual, and such web handles are then replaced byndfSDpFDA. For example, the hWeb can use Joe.GM.com/sedans,Joe.GM.com/Buick, and Joe.GM.com/Chevy.

[0343] 4. The hWeb be modified such that when using the ndfSDpFDA as itsindividual's representation system, the hWeb can also Internet addresssuch ndfSDpFDA, and extract data field information from http://ndfSDpFDAto be used for representation and identification information.

[0344] 5. The hWeb be modified such that in addition to #3, a nSD textcan represent the individual's identity information for all itsndfSDpFDA family. The identity can be used in computing routines such asindividual branding characteristics, billing and shipping address,account information, and more.

[0345] In short, instead of the web handle system, IWebs use ndfSDpFDAs.The IWeb further searches and extracts the data field information froman individual's http://ndfSDpFDAs profiles to gather furtherrepresentation and identity information on the individual. The IWebs canparse the ndfSDpFDA to use the text of nSDs for individual identity.

[0346] The result is that IWeb treats ndfSDpFDAs very differently thanhWeb treats web handles. First, unlike a web handle, the ndfSDpFDA canbe quickly web addressed (by prefixing http://) to attain web profileinformation. Next, when hyperlinked, the ndfSDpFDA is humanly readableas hyperlinked to http://ndfSDpFDA. Furthermore, an IWeb can acceptseveral ndfSDpFDAs from a single individual. For example, in a commerceIWeb, an individual may use a FD for his sports sale items, a FD for hisstamp collection, and a FD for his automobiles. Yet, IWeb can identifyhim through his single nSD text.

[0347] Where an IWeb uses multiple FDs of a single ndfSDpFDA family, theIWeb, unlike hWeb, may further process his multiple ndfSDpFDAs foradditional individual information. Such processes may be, for example,taking an average of customer ratings for the ndfSDpFDA family members,accumulating all sales activities of the ndfSDpFDA family members,providing a single accounting system for the family, and more.

[0348] A significant time-saving advantage for the individual is that,unlike hWeb and web handles, the individual's same ndfSDpFDA can be usedin many IWeb websites. To attain a hWeb web handle, the individualusually types his individual information into registration formssupplied by the hWeb. Such information can include his name, address,occupation, and age. Using IWebs and ndfSDpFDA, the individual simplyenters in his relevant ndfSDpFDA for that IWeb website, and the IWebextracts the information from the entered http://ndfSDpFDA'sexchangeable data. The same ndfSDpFDA can then be entered into otherIWeb websites, saving him tremendous amount of user registration time,and enabling him to quickly carry his identity and representation toother websites. For example, Joe of GM (from above) can quickly enterJoe.GM.com/sedans at multiple IWeb sites offering car sales and enterJoe.GM.com/technical (below section XII & XIII) at multiple IWebemployment sites.

[0349] Notice in the below section that the types of data exchanged bythe various ndfSDpFDAs to the IWebs are quite different. In the abovecontact manager, we saw contacts information. In below, there arecommerce, dating, employment, political, social, security, and othertypes of information. ndfSDpFDAs and IWebs are flexible and wide-rangingin the type of data fields that are utilized, which is different fromother forms of individual identification, representation and exchangesystems.

XI. Impact of the ndfSDpFDA and Additional Embodiments

[0350] Changing the hWeb to an IWeb by changing web handles to ndfSDpFDAin a system may appear to be a minor convenience, but its social,political, economic, and Internet impact can be great.

A. eCommerce

[0351] Consider the case of eCommerce and a hypothetical dominant webindividual auction site, Monopoly.com (for example, eBAY.com).Monopoly.com provides a way for individuals to auction products, andowns 70+% of its marketplace. The barriers to entry in Monopoly.com'smarketplace are: its brand name, its numbers of buyers and sellers, andthe amount of time it takes for an individual to list his products withanother website. Let's suppose new hWeb websites Competitor1.com,Competitor2.com, . . . , and CompetitorN.com offered identical servicesas Monopoly.com, and offered these with a promotional offer of notransaction fees for three years. Such competitors still face a highbarrier to entry because it takes time for a seller to list his productsat each Competitor's site, and listing at these new sites with fewbuyers would multiply his time costs of selling tremendously.

[0352] Suppose the seller received a webpage designed for eCommerceexchanges at one of his ndfSDpFDA page (e.g., his own eCommerce onlinecatalogue). This webpage enables him to list all his products for sale,and carries data fields and data for his products. After listing once,the seller can quickly enter this ndfSDpFDA to sell at the newly revisedCompetitor1.com, Competitor2.com, . . . , and CompetitorN.com IWebs. Theimpact is that one of Monopoly.com's major barriers-to-entry (listingtime) nearly disappears (particularly true if Monopoly.com also usedIWeb). Using IWebs instead, Competitor1.com, Competitor2.com, . . .CompetitorN.com's promotional offer of no listing fees coupled withminimal time required for product listing, will motivate individualsellers to list with them, and over time, will form a sizable salesinventory. Buyers can also register quickly at these CompetitorN.comIWebs by conveniently entering in their purchasing ndfSDpFDArepresentations.

[0353] The result is that many competitive marketplaces will emerge tocompete against the dominant Monopoly.com. And with more competitivesites, the power and focus of the eCommerce shifts to the individualrather than to dominant websites. Service prices drop, serviceselections improve, and more and better commerce develops.

B. Matchmaking

[0354] Another case is matchmaking sites. Again, many quality sitescreate a barrier to entry by having a lengthy dating questionnaire forindividuals. Once the individual completes it, he is reluctant to visitanother site to fill out another lengthy questionnaire. In usingndfSDpFDA and IWeb matchmaking sites, the applicant is able prepare hisdating profile ndfSDpFDA webpage, and then quickly enter this ndfSDpFDArepresentation to many matchmaking sites, thereby, improving the degreeof competition in the dating marketplace.

C. Employment

[0355] Another case of hWeb to IWeb benefits is the employment websites.The job applicant can quickly submit his ndfSDpFDA employmentinformation to several IWeb employment websites instead of having tofill out extensive forms for each site. Again the power shift andconvenience favors the Individual rather than the websites. This isdescribed in detail with Joe of GM.com's work experience profiles below.

D. Political and Social IWebs

[0356] IWebs and ndfSDpFDAs will also impact political and socialorganizations. These organizations rely heavily on the participation ofindividuals. In most prior-art websites, the individuals typicallyreceived an email newsletter, a public announcement website andweb-handled discussion forums. Yet, the individual is not wellidentified and represented when if if he participates in this prior artwebsite.

[0357] Using an IWeb with the organization's domain name and ndfSDpFDA,the political and social individuals can better identify and representthemselves better and learn more about other individuals in theorganization. This improves networking and bonding through the IWeb,allows for identified discussion forums, enables better organization andassignment of responsibilities, and improves communications amongindividuals. These IWebs will improve political and socialorganizations, will create new forms of associations based on common-affiliations-with-same-domain-name-website, transcend borders, and willchange the way people participate politically and socially worldwide.

E. Alumni Websites

[0358] Still another case is web networking services for college alumni.In prior arts, the alumni are typically given a web handle or use theirreal name and then possibly participate in the alumni's discussionforums and directories. Yet, the purpose of much of this networking isto simultaneously establish a business networking relationship. UsingIWebs' discussion forums, the alumni can enter in the alumni IWeb andthen participate using their business firm's issued ndfSDpFDA, thusquickly identifying and promoting their business interests while alsoparticipating in and promoting the school's activities.

F. Digital Identification

[0359] Major firms are trying to set standards in a field known asdigital identification (http://www.digitalidworld.com/index.php).Microsoft's entry, Passport, has many commerce transactionauthentication features, and is backed by the power of a monopoly. Butit lacks an individual's representation that is useful in digital andnon-digital communication channels and that is communicable byindividuals to website as well as by individuals to individuals, such asndfSDpFDA & IWeb has and can. As such, Passport has been mildly received(relative to its expectations). Furthermore, many powerful interests,including credit card companies, computing companies, banks, etc. refuseto partner with Passport in part because they fear Microsoft's monopolycontrol and Passport's information gathering would lead to Microsoftcontrolling information on their valuable customers' base.

[0360] Passport-technology-like (Passport-like) products' marketplaceacceptance can be easier achieved through coupling ndfSDpFDA withPassport-like products. The ndfSDpFDA can provide representationinformation about the individual, and Passport-like products provideauthentication about financial information for when the individualconducts eCommerce. The ndfSDpFDA is useable by websites and otherindividuals seeking to identify the ndfSDpFDA; whereas, Passport-likeauthentication system is useful primarily by websites. Thus thiscombination introduces Passport-like authentication to a wideraudience's acceptance.

[0361] Firms concerned about Microsoft's monopoly position can, insteadbe brought in as allies on Passport-like technologies for financialauthentication. The firms can brand the ndfSDpFDA or link through this,and then utilize a Passport-like technology in the background; hence,the firms have greater control and would feel less threatened by amonopoly control. Again, ndfSDpFDA reduces the monopoly control by afirm while providing better representation to websites and otherindividuals. By coupling ndfSDpFDA identity and representation withPassport-like technology's financial authentication, a better financialservices system results.

G. National Defense

[0362] IWebs and ndfSDpFDA are mutually enhancing—that is, increase thepopularity of one, and the other's popularity will also increases. Anincrease in use of ndfSDpFDA can also have tremendous social impact.Take for example the area of national defense. Presently, there aredevices such as eye scanners, fingerprinting systems, passports, driverlicenses, etc. to identify individuals. However, scanners andfingerprinting systems are not useful on a small scale. For example, aterrorist can bomb a small building, but it would be too expensive toinstall and operate these specialty devices in smaller buildings. Howdoes anyone working in the small building identify a stranger who entersthe building?

[0363] The stranger's organization or a special federal agency cancreate a ndfSDpFDA certification administrator, who certifies, on behalfof the organization or agency, the stranger's certified ndfSDpFDAwebpage, transmitted by the secure https protocol if desired. The users(stranger) are unable to change a certified ndfSDpFDA's web content, andsuch content states the certifier authority.

[0364] The small building's staff can check out the stranger byreviewing a ndfSDpFDA provided by him. https://ndfSDpFDA orhttp://ndfSDpFDA would show the stranger's photo and information. If thebuilding's staff then trusts the organization's domain's certifier orthe federal agency certifier, then, it relies on this information tocheck on the stranger. No extra specialty equipment, extra telephonecalls, carry-ID photographs, biometric devices, and other traditional orexpensive methods is needed-just simple access to the Internet. If thestaff does not trust the certifier, then more extensive investigationswill be needed. Nevertheless, the cost of national defense is reducedthrough the usage of this inexpensive individual identification system.

[0365] For example, Gail Smith of FBI.gov has the ndfSDpFDA ofGailSmith.FBI.gov/generalID, which carries her photo, states she is aFBI employee, and certifies that FBI has reviewed her information. GailSmith is unable to change the content of this webpage, or her subdomainname; these are under the control of FBI.gov's certifier. The securitysystem can even be made such that only the certifier can change her filedirectory name (through passwords only known to certifier, or this pFDchange process does not allow for certified FDs to be changed byuncertified individuals). If the building staff trusts the domainFBI.gov, they will then be able to identify Gail Smith through herphoto. If Gail Smith made a telephone call to inquire for information,the building staff access http://GailSmith.FBI.gov/generalID, determineif they trust the domain name FBI.gov and its certifier, and if so,notice Gail Smith's telephone number listed, and call that FBI number—tomake sure it is Gail Smith who made the telephone call. Likewise Joe ofGM.com can be identified thus, if the user trusts GM.com. Notice that bychecking the domain name and reviewing its reputation, the building caninfer the quality of the certification of the ndfSDpFDA page. These arelow level of security checks; yet, it is very inexpensive and can beimplemented worldwide easily.

H. Summary of Section XI Cases and Embodiments

[0366] In numerous cases above—contacts management, eCommerce,matchmaking, employment, national defense, digital identification,alumni directory—the impact of using ndfSDpFDA to participate in IWebsis shown to be able to shift the entire economic, power, social, andpolitical structure of the Internet and the world.

XII. IWeb's Individual Identity—the Text of the nSD

[0367] Using Table 1's data, an IWeb can identify the individual by hisfirst and last names. But how will an IWeb identify same nameindividuals? More importantly, first and last names may not be availablein many IWebs. And other means of identification have restrictions.Social Security numbers would be useful only to United States workers.Most people are reluctant to release credit card numbers to be used aspublic identity. eMail addresses of syntax name@adomain.com arespammable.

[0368] Both hWeb and IWeb gather information on and track theindividual's identity and representation information. Such informationmay include the individual's reputation, billing, contact, shipping, webstatistical, demographics, and other information. Such can be seen ineBay.com and Matchmaker.com websites.

[0369] To better understand identity and representation, take for theexample, a marketplace site designed for individuals to sell fourwheeled cars. hWeb software, such as prior arts software running eBay ora classified car marketplace site, would require their own unique webhandle system for individuals' representations. Web handle examples are“fromglobaltoyou”, “browneyedgirl022”, “faithingintheprize”, “beauty25”,“lively505”, and “beach296”, where these represent and identifyindividuals.

[0370] Instead of using web handles, IWeb can use ndfSDpFDAs for theIWebs' individuals' representations—for examples (returning to Joe ofGM's profiles in section III above) Joe.GM.com, Joe.GM.com/Buick,Joe.GM.com/Chevy, Joe.GM.com/sedans, and Joe.GM.com/56kje26, as well as,Mary.Ford.com/Mustang, Kate.Mercedes.com/trucks, andChen.WebAndNet.com/personalcar. All these ndfSDpFDAs have associatedexchangeable information and can contribute to this IWeb's overall carsales. Unlike hWeb, an IWeb can use multiple ndfSDpFDA representationsof an individual. A single IWeb can also use multiple domain names inits ndfSDpFDAs.

[0371] We can understand the concepts of individual identity and profilerepresentation in an IWeb through the Joe of GM.com example from above.Http://Joe.GM.com has sparse and public information and, in thisinvention's system, none of Joe of GM's FD profiles is continualinformation, as Joe.GM.com's FDs can change. Hence, no one of Joe's FDnames, DFD (domain-file-directory) combination names, or profiles can beused for adequate Joe identification for the IWeb.

[0372] Let's also review an employment IWeb site. Joe may wish to useseveral resumes. For example, http://Joe.GM.com/technical shows histechnology resume; http://Joe.GM.com/management shows his managementskills; http://Joe.GM.com/sales shows his sales experience. Each of thendfSDpFDAs, when addressed, can show exchangeable resume data fields tothe IWeb. For example, Joe.GM.com/technical and Joe.GM.com/sales mayshow, when addressed, XML fields that reflect various programminglanguages he's familiar with and years of sales experience.Joe.GM.com/management may show, when addressed, HTML commentary fieldsindicating his years of management experience.

[0373] Both the car and employment IWebs need to identify and track theindividual Joe of GM.com with his IWeb-participating profilesinformation—to establish an identification for Joe to be used formatters such as credit worthiness, buyers' rating systems, shippingaddress, etc.

[0374] As explained above, an individual's subdomain and domain namesare usually continual. By using the text of the “nSD” (not the same ashttp://nSD), this forms an unique identity system that is continual.Recall that a ndfSDpFDA family of profiles has the same nSD text. Hence,the nSD text portion of the ndfSDpFDA can serve as the individual'sidentity in an IWeb. And because the http://nSD is unique in theInternet (due to DNS), this same nSD text can be used by many IWebs toidentify the same individual. Note that here the term “represent” herereflects the individual's ndfSDpFDA's web profile and profile contentand is different from the term “identify”, his individual's identity tothe IWeb site. (Note also that an individual may have severalidentities, by having his name associated with several domain names in anSD syntax. IWeb would see each such identity as distinct).

[0375] Hence, the individual identity used by IWeb is the nSD textportion of the ndfSDFDA. This is accomplished by the IWeb parsing thendfSDpFDA for the text nSD. In the example used, it “Joe.GM.com” is theidentity. This is not the same as the http:H/Joe.GM.com address or itsweb content. The various Joe.GM.com/FD, including Joe.GM.com/sedans,Joe.GM.com/Chevy, Joe.GM.com/managerial, Joe.GM.com/technical, . . . arerepresentations and when addressed are profiles. The “Joe.GM.com” textas identity is the same as the Joe.GM.com as nSD, but without theinference that it relates to the web content of http://nSD(http://Joe.GM.com).

XIII. IWeb, nSD, and Branding

[0376] Also, because the various IWebs can keep track of the individualthrough nSD-text-as-identity; and because the http://nSD is an uniqueidentity due to DNS and is web addressable with web content; theindividual's nSD-text-as-identity branding characteristics can beestablished across multiple IWebs, as well as across the Internet. Oneway is that each IWeb can submit a rating of an individual'snSD-text-as-identity to a rating service and the cumulative result ofhis IWebs' nSD-text-as-identity ratings is seen as the an individual'sInternet branding characteristic. For example, if Joe of GM.com sellscars at hypothetical IWeb websites such as autosales.com, carsales.com,autoauctions.com (and someday IWebs eBay.com and Yahoo.com), all thesesites could submit buyers' feedback for Joe.GM.com's various profiles toa seller's rating service, which would provide a cumulative rating forJoe.GM.com, and hence branding for the individual Joe of GM.com.Likewise for a Betty.Ford.com, Jack.Mercedes.com, Fran.Honda.com . . . .

[0377] ndfSDpFDA ratings can be further accumulated to form a rating forthe domain. Since the domain represents the organization (as explainedabove), this then can become the rating and branding for theorganization. Hence, if several employees of GM.com using n.GM.com/FDprofiles (with their own “n” names) were to receive poor ratings, theircumulative poor rating would result in a poor rating for GM.com. Suchcan be accomplished by computing algorithms that average the accumulatedratings for GM.com's ndfSDpFDAs.

XIV. ndfSDpFDA Web Content Authorizes Interaction With IWeb

[0378] It preferred that http://ndfSDpFDA displays which IWeb websitesare authorized to interact with it. For example, Joe of GM wants to sellhis sedans in hypothetical IWeb websites autosales.com and carsales.com,but not at autoauctions.com. Joe enters a private (password protected)user-input, authorization module webpage and he inputs the texts“autosales.com” and “carsales.com” as authorized IWebs forJoe.GM.com/sedans. Through web database and other known programmingtechniques, http://Joe.GM.com/sedans then displays, in an “IWebauthorization” data field exchangeable section, that “autosales.com” and“carsales.com” are authorized IWebs.

[0379] A coding mechanism is set up for the “IWeb authorization” datafield. An IWeb extracts and assesses its authorization before acceptingan ndfSDpFDA as a participant. For example, using the HTML commentariesmethodology described above, “autosales.com <!—Iweb authorizedwebsite—>” can be extracted as a data field. Autosales.com willsubsequently authorize “Joe.GM.com/sedans” as participant inautosales.com's web marketplace. XML and other data communicationsmethodologies can also be used to designate authorized fields.

[0380] An unauthorized IWeb may ignore its authorization status and cancontinue to participate an ndfSDpFDA's web content and representation,but the IWeb's users can check http://ndfSDpFDA as to correctauthorization. An ndfSDpFDA may also block an unauthorized IWebparticipation usage by refusing to supply data field information to anunauthorized IWeb's URL call.

[0381]FIG. 20 shows the above processes. Http://ndfSDpFDA(Joe.GM.com/sedans) webpage (1) displays a set of authorized websites'names, “autosales.com” and “carsales.com” (2). Joe of GM.com had entereda private “site authorization” module webpage (3) and inputted (4) innames of authorized IWebs. This module then incorporates (5) these namesas part of the web display content of http://Joe.GM.sedans in a sectionwith data fields for IWeb authorized sites. This incorporation can beaccomplished by several methods, which are known to web programmers. If,for example, the http://Joe.GM.com/sedans is created by a web database,the database would incorporate and display the IWeb names throughpreviously programmed database routines. If, instead,http://Joe.GM.com/sedans is a static webpage, programming routines wouldadd the IWeb names as part of authorized IWeb data fields in the staticwebpage. Numerous other incorporation means are known.

[0382] Http://Joe.GM.com webpage then displays these authorized websites(2). The IWebs autosales.com and carsales.com can extract (6) data fieldinformation from http://Joe.GM.com/sedans and determine (7) their statusauthorization through the data of the authorized IWeb sites section (2).Being authorized, autosales.com and carsales.com can then useJoe.GM.com/sedans additional data fields' information to sell and buycars for Joe (9).

[0383] Unauthorized IWebs can also extract Joe.GM.com/sedans's datafield information. These may have policies (8) to excludeJoe.GM.com/sedans from participation (10). Or, these may have policies(8) to ignore their authorization status and participateJoe.GM.com/sedans (11); in which case, users will have to checkhttp://Joe.GM.com/sedans for authorization status (12) to ensure Joe ofGM.com approves of the interactions.

[0384] Routines can be programmed whereby only the authorized IWeb canextract selected data field information. For example, the ndfSDpFDA'sweb server would identify an IWeb's URL call request and ip address (13)and release data field structure and/or information only to theauthorized ip requests (14) (15). The ndfSDpFDA owner had previouslyinputted authorized IWeb ip addresses in step (4). In this way, thehttp://ndfsDpFDA can refuse unauthorized data extraction URL calls.

[0385] For example, a http://ndfSDpFDA may display no data fieldinformation to all URL calls except when the call originates fromauthorized ip addresses. This can be accomplished by detecting ipaddresses and changing web content depending on the ip address. The webserver and the ndfSDpFDA would detect the originating URL call's ipaddress, and, when authorized, return with webpage content whichcontains the HTML commentary fields or XML used as data fields.Unauthorized URL calls (as detected by their ip addresses), whenattempting to extract data fields, would receive web content without thedata field structure or would not receive reply.

XV. Variants

[0386] nURLv s other than ndfSDpFDAs can be used for nURLv-IWebinteractions and for individual representation and identity. Forexample, ndfSDpFSA can be used with equal technical capabilities, but itis not preferred because it is more difficult to verbally communicate.IWebs can accommodate many types of nURLvs, as will be explained.

[0387] Other variants are that sub-subdomain domain file directorynaming syntax (e.g. Bob.Jones.CompanyA.com/biz) may be used. Theaddressing principles here work the same as the above because of thehierarchical structure and nature of DNS, Internet, and web serveraddressing schemes. Those knowledgeable in DNS structures and webaddressing would know this. Also, higher still order subdomains andlonger file suffixes can be used.

[0388] Another variant is that the FD/ (with the ending “/”) is usedinstead of the FD. The FD/ version may be more efficient for the httpaddressing, but it is longer to communicate (particularly when spoken),hence the FD version is preferred.

[0389] Also in many circumstances, it would be useful for individualsother than web administrators and programmers to change n of nSD. Forexample, an individual who gets married can have an automated means tochange her name rather than to wait on the domain administrators. Theabove examples, particularly in FIGS. 7 and 8, show that this ispossible to design by placing the pcsm module starting at step13 wheresubdomain names are requested (explained above).

[0390] Also, the physical host and its communications lines of the IWebsoftware can be important. If the IWeb is located on a single host withthe rest of the SDFDs, it would not require http access to attain itsndfSDpFDA data. Http is a non-continual state protocol, and itsprogramming is much more difficult. By having the IWeb and the SDFD on asingle host (or connected through high speed data lines not requiringhttp), this can make IWeb and ndfSDpFDA interactions much easier, accessmuch faster, and programming much easier.

[0391] The public communications channel can reside on ndfSDpFDAs otherthan the nSD.

[0392] The nSDFDAs can also be located in a palmtop or kiosk instead ofa personal computer and use a different kind of Internet client than aweb browser. The operating system of the servers can change toMicrosoft's Windows NT Server, the web server can change to Microsoft'sInternet Information Server. Other operating systems and web servers canalso be used. Users' operating system can certainly be other versions ofWindows as well as non-windows operating systems. In still otherembodiments, add-on applications may be used to expedite datatransmissions and make the searches more user-friendly and fast.

[0393] Where the words “personal computer” or “local” are used, thesecan represent workstations that are part of a local area or wide areanetwork. Here, instead of accessing nSDFDAs on a local hard disk,nSDFDAs may be on the network's hard disk. The technologies for localand wide area networks are well understood, and the terminologies above,when referred to as local, applies to the technologies of these localand wide area network devices.

[0394] Physical location of the various components may also differ. Forexample, in IWebContacts, it sometimes makes very little differencewhether the routine that generates the “Add nSDFDA” box comes from a webserver or a personal computer.

XVa. Variant: “df” Not Required on IWeb

[0395] Most IWebs will use “df's, and as such, ndfSDpFDAs are thepreferred nURLv. There will be circumstances where the “df” (datafields) is unimportant, as for example in the discussion forums. Herethe nSDpFDAs can be used to represent individuals. Associatednon-data-field web content (e.g. HTML webpage without data fields) canbe used to represent the individuals. These nSDpFDAs are used very muchlike web handles, except that they have the additional capabilities ofbeing easily hyperlinked to be Internet addressed (by simply addinghttp:// and of being humanly visibly understood as hyperlinked to orhaving the address of http://nSDpFDA. For example, in a discussionforum, a user can click an individual participant's nSDpFDA hyperlinkedlink, and the individual participant's http://nSDpFDA profile comes upon another browser. This user simply wishes to read the individual'sprofile's non-data-field webpage (HTML) information.

[0396] Another example can be an association members' web index, wherethe members' nSDpFDAs are hyperlinked to http://nSDpFDA and are arrangedalphabetically, and one can click these to read a member's profile on awebpage. Still another example is where the IWeb arrange the ndfSDpFDAnames in a set order, and use it as a hyperlinked index, without havingto pull in the data fields of the nURLvs. In these and other cases, thenSDFD, nSDFS, nSD can be effectively used by the IWeb.

XVb. Variant: IWeb and the Privacy Module in ndfSDpFDA

[0397] IWebs generally do not automatically know whether the privacymodule has been included, as after the privacy module works, the IWebreceives the new nSDFD and may not be able to accurately check whetherpcsm was used without using special routines. Where IWebs use ndfSDpFDAor ndfSDpFSA, the ndfSDFDA or ndfSDFSA versions (without the privacycontrol) can also be frequently used, as in the example of theIWebContacts above. Special routines can be added to detect the changesin pFD. For example, the user may voluntarily inform (submit to) theIWeb that a change in pFD has occurred, and the IWeb revise itsinformation accordingly. Or, the IWeb may be able to detectcharacteristics of the second pFD, as IWeb has the individual's nSD nameand history, to determine whether its web content the same as the firstpFD.

XVc. Variant: Visitor's Introduction nURLv Input Field

[0398] When a visitor visits the http://ndfSDpFDA with the publicchannel of communications (usually http://nSD), the visitor can quicklyintroduce himself by typing in his own ndfSDpFDA into a visitor's inputbox on the same webpage as the public channel communications webpage.For example, if Joe of GM.com visits http://Chen.WebAndNet.com, he caninput “Joe.GM.com/Buick” into http://Chen.WebAndNet.com's user-input boxfor visitor's ndfSDpFDAs, and Joe.GM.com/Buick will be forwarded to Chenfor Chen's introduction to http://Joe.GM.com/Buick.

XVI. Summary

[0399] The above invention forms an individuals' exchange systemcomprising of:

[0400] 1. a nURLv system of ndfSDpFDA with the person's name as thesubdomain and having exchangeable data with an IWeb.

[0401] 2. The http://ndfSDpFDA which can offer privacy control bychanging the file directory name,

[0402] 3. a spam-resistant communications channel addressable throughnSD,

[0403] 4. a individuals' exchange system (IWeb) that can use thesendfSDpFDAs for individual representation and exchange,

[0404] 5. A branding of the nSD individual established through IWebsaccumulating information on the ndfSDpFDA,

[0405] 6. A branding of the domain organization established throughIWebs accumulating information on the ndfSDpFDA, and

[0406] 7. A means whereby ndfSDpFDA can authorize which IWebs can useits exchangeable data fields.

[0407]FIGS. 4 and 12 show the overviews of this invention, FIGS. 5-11show various pFD processes and ndfSDpFDA embodiments, FIG. 13-19 show anembodiment of a contacts manager, and FIG. 20 shows the authorizationprocess. Several detailed embodiments of alayman-user-friendly-FD-change-processes are detailed, an embodiment ofan IWeb-ndfSDpFDA interaction of a contacts manager is detailed, andeCommerce, matchmaking, employment, discussion forum, and politicalorganization embodiments, usefulness, and impact are explained.

[0408] While the disclosure contained herein has set forth severalembodiments of the invention, and many of the fundamental componentsused within the invention are well known within the art, it will beappreciated by those skilled in the art that variations to thecombination of elements and steps disclosed can be made withoutdeparting from the scope and spirit of the invention.

1. A system using the non-protocol portion of a Universal ResourceLocator names to represent individuals by: a. Having the individual'sname or representation of his name as the third level domain name(subdomain) associated with a second level and first level domain names,and b. Having file directory names for the above such that using hisname-subdomain-file directory combination can show, using the Internethttp addressing, his differing web content (profiles) for different filesuffixes, c. giving the individual the ability to change his filedirectory name while retaining its original web content, and d. havingthis name change process such that it is layman user friendly, such thatthe individual can have an easy way to communicate his representation,have profiles of his communicated representation be addressable andshown on the Internet.
 2. A system of websites comprising of a. Usingfor its individuals' participants representationsname-Subdomain-Domain-File Directory syntax, b. means of extracting datafields and data from the webpages of such syntax c. means ofmanipulating data extracted, and d. means of presenting such manipulatedinformation using the Internet, such that these websites can form a formof individuals' exchange system.
 3. The website in claim 2 appliedtoward eCommerce a. Whereby each individual has his ownname-subdomain-domain-file directory website address to use to as anidentity within an eCommerce site.
 4. The websie in claim 2 appliedtoward employment a. Whereby each individual has his ownname-subdomain-domain-file directory website address to use to as anidentity within an employment site.
 5. The websie in claim 2 appliedtoward matchmaking a. Whereby each individual has his ownname-subdomain-domain-file directory website address to use to as anidentity within a matchmaking site.
 6. A contacts management system thatcomprises of the claims 2 and is a. capable of extracting contactsinformation from the data and data fields, and b. capable ofmanipulating contacts information, such that a business card and moreinformation can be easily transferred and exchanged.
 7. A contactsmanagement system that comprises of the claim 6 and is able to provideconsolidated profile information about an individual by: a. Using asystem of prioritization and consolidation to manipulate its storedidentities such that fuller and easier views of individuals areavailable throught he contact manager.
 8. The addressing system in claim1 a. with the added feature of having a public communications,spam-resistant communications system added to its name-Subdomain-Domainaddress such that a public, easy-to-recall communications system can beset.
 9. A method in which the addresses in claim one a. Carryauthorization information for which websites are authorized to extractand participate its information such that an approval-for-use procedureis available for the individual.
 10. A method to establish personalbranding characteristics by a. Using the text portion of thename-Subdomain-Domain portion of a name-subdomain-domain-file-suffix orname-subdomain-domain to establish identity in websites, b. allowing thewebsites to rank the personal identity c. consolidating the variouspersonal identities such that personal branding characteristics can beestablished on the Internet.
 11. A system of using layman-changeablefile directory names in claim 1 further comprising of:
 1. a module toenable for the change of the directory name to a second name,
 2. amodule that erases or redirects the first name, and
 3. a web entry pointfor this change, such that a layman can change his file directory in anaddress system to preserve privacy.